Re: libxalan-java

2004-02-19 Thread Arnaud Vandyck
Stefan Gybas <[EMAIL PROTECTED]> writes: > Jan Schulz wrote: > >> Sorry, for all the inconvinience. I completly missed the 'source' here. > > Well, the binary package would also be called libxalan-java. The > packages that are ready to go to main are available at > http://people.debian.org/~sgybas

Re: libxalan-java

2004-02-19 Thread Stefan Gybas
Jan Schulz wrote: Sorry, for all the inconvinience. I completly missed the 'source' here. Well, the binary package would also be called libxalan-java. The packages that are ready to go to main are available at http://people.debian.org/~sgybas/java/. All but libxalan-java have been uplodaded are

Re: libxalan-java

2004-02-19 Thread Arnaud Vandyck
Jan Schulz <[EMAIL PROTECTED]> writes: > Hallo Arnaud, > > * Arnaud Vandyck wrote: >>Jan Schulz <[EMAIL PROTECTED]> writes: >>I agree, but with you should read the arguments of Stefan: I'd like to name the new source package in main libxalan-java > ^^ > Moep..

Re: libxalan-java

2004-02-19 Thread Arnaud Vandyck
Jan Schulz <[EMAIL PROTECTED]> writes: > Ok, so I misunderstood, what the libxalan-java package is about. On > the other hand, I don't understand things like that then: > > apt-cache show fop: > [...] > Depends: java-common, j2re1.3 | j2re1.4 | java2-runtime, > libxerces-java, libxalan2-java, libb

Re: libxalan-java

2004-02-19 Thread Stefan Gybas
Jan Schulz wrote: It seems that some packages use xalan directly and having it upgrading I've not looked at fop but as I've said, the currently packaged libxalan2-java includes additional external classes in xalan2.jar and FOP might use them to access the XSL transformer. to a newer breaking AP

Re: libxalan-java

2004-02-19 Thread Jan Schulz
Hallo Arnaud, * Arnaud Vandyck wrote: >Jan Schulz <[EMAIL PROTECTED]> writes: >I agree, but with you should read the arguments of Stefan: >>> I'd like to name the new source package in main libxalan-java ^^ Moep... Sorry, for all the inconvinience. I completly mis

Re: libxalan-java

2004-02-19 Thread Jan Schulz
Hallo Stefan, * Stefan Gybas wrote: >Xalan and Xerces don't not have external APIs themselves. The API for >Xalan is TrAX and packaged in libjaxp1.2-java. If some packages are >using internal classes directly (like Xalan does with Xerces), they are >basically on their own. It's like application

Re: libxalan-java

2004-02-19 Thread Arnaud Vandyck
Jan Schulz <[EMAIL PROTECTED]> writes: > Hallo Stefan, > > * Stefan Gybas wrote: >>I'd like to name the new source package in main libxalan-java (instead >>of libxalan_2_-java) since that's also the name that upstream uses. > > IMO that as bas as using kdelibs instead of kdelibs4 > > Jars like x

Re: libxalan-java

2004-02-19 Thread Stefan Gybas
Jan Schulz wrote: Thats also the reason, why the proposed policy uses '[-].jar' and 'lib-java' as names for jars and packages. Xalan and Xerces don't not have external APIs themselves. The API for Xalan is TrAX and packaged in libjaxp1.2-java. If some packages are using internal classes directly

Re: libxalan-java

2004-02-18 Thread Jan Schulz
Hallo Stefan, * Stefan Gybas wrote: >I'd like to name the new source package in main libxalan-java (instead >of libxalan_2_-java) since that's also the name that upstream uses. IMO that as bas as using kdelibs instead of kdelibs4 Jars like xalan are libraries and should be packaged accordingly