Bug#417888: state of the batik package

[Vincent Fourmond]

  Hello !

Torsten Werner wrote:
> what is the state of the package. What needs to be done before it can
> be uploaded to unstable? Do you need any help?

  It was waiting for xml-commons-external to get into experimental.
We'll have to upload first to experimental, as the upgrade can
potentially break many packages.

  Another guy, Sylvestre Ledru <sylvestre.ledru at inria.fr>, also showed
interest in batik. I don't know how we should best coordinate efforts,
if you want to participate. Do you reckon debian-java at l.d.o would be the
right place for that ?? Or, probably better, we should discuss that on
the mailing list in bug #417888, in CC  ?

  Right now, I'm also working on a new version of java-wrappers, with a
hint more flexibility and usability. I plan to use it for the
executables found in the package.

  The work on batik is basically the following:

  * make sure it works fine with openjdk, which means that we need to
check that all the executables all have around the same behaviour with
sun-java-* and openjdk-*. Fortunately, this should be very easy with new
features of the java-wrappers script.

  * make sure the interface didn't change too much, and in particular
that the reverse dependencies work fine with it, including with openjdk.
That will be more painful than the previous point. My opinion is that we
should upload a preliminary package to experimental, ping the reverse
dependencies, and when they have checked them decently enough, upload to
unstable.

  At any rate, no hope for batik to make it into lenny, sadly.

  Cheers,

	Vincent

-- 
Vincent Fourmond, Debian Developer
http://vince-debian.blogspot.com/

The Librarian was, of course, very much in favour of reading in
general, but readers in particular got on his nerves.
 -- Terry Pratchet, Men at arms

Vincent, listening to Southbound Again (Dire Straits)