On Fri, 2005-04-15 at 12:14 +0200, Arnaud Vandyck wrote:
> Wed, 06 Apr 2005 10:42:51 -0300,
> Martin Ferrari <[EMAIL PROTECTED]> wrote:
>
> > I didn't know about build problems with libxalan-java. I am a sysadmin,
> > so I don't directly use it, but instead
Wed, 06 Apr 2005 10:42:51 -0300,
Martin Ferrari <[EMAIL PROTECTED]> wrote:
> I didn't know about build problems with libxalan-java. I am a sysadmin,
> so I don't directly use it, but instead the local programmers use it,
> and I've made a bunch of debian packages o
Hi!
On Wed, 2005-04-06 at 15:15 +0200, Wolfgang Baer wrote:
> > Well, not having dependencies doesn't mean they aren't used! For
> > instance, I use libxalan-java!!
>
> Hi Martin,
>
> where do you need libxalan-java ? Can't you use libxalan2-java instead
Martin Ferrari wrote:
On Tue, 2005-04-05 at 15:28 +0200, Arnaud Vandyck wrote:
Mon, 28 Mar 2005 16:51:22 +0200,
Wolfgang Baer <[EMAIL PROTECTED]> wrote:
this is another RFC for the removal of libxalan-java
and now also lib-saxon-java
Both are no longer used in build depends nor runtime
d
On Tue, 2005-04-05 at 15:28 +0200, Arnaud Vandyck wrote:
> Mon, 28 Mar 2005 16:51:22 +0200,
> Wolfgang Baer <[EMAIL PROTECTED]> wrote:
> > this is another RFC for the removal of libxalan-java
> > and now also lib-saxon-java
> >
> > Both are no long
Mon, 28 Mar 2005 16:51:22 +0200,
Wolfgang Baer <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> this is another RFC for the removal of libxalan-java
> and now also lib-saxon-java
>
> Both are no longer used in build depends nor runtime
> depends. lib-saxon-java is superseded
Hi all,
this is another RFC for the removal of libxalan-java
and now also lib-saxon-java
Both are no longer used in build depends nor runtime
depends. lib-saxon-java is superseded by libsaxon-java,
but is still in the archive.
If no objections will show up in the next days I will
file a removal
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 av
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
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
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,
>
r breaking API version will break this apps. Therfore I think
it would make some sense to treat this packages 'as API' as long as we
have software, which uses internal API.
The API will stay comaptible. As I've said, the new Xalan version is
compatible with what is currently packag
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
ir own. It's like applications that might break when
>they are using internal libc6 references.
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 |
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 usin
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
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 sh
Hi!
I've managed to build Xalan-J 2.5.2 with Kaffe and Jikes and it even
seems to run with Kaffe. So the main Xalan package could go into main!
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
According to http://bugs.debian.org/#200460
What is the status/ decision about that?
Best regards,
-- Arnaud Vandyck
http://alioth.debian.org/users/arnaud-guest/
http://alioth.debian.org/developer/diary.php?diary_user=2781
pgpbDCkdajAol.pgp
Description: PGP signature
According to http://bugs.debian.org/#200460
What is the status/ decision about that?
Best regards,
-- Arnaud Vandyck
http://alioth.debian.org/users/arnaud-guest/
http://alioth.debian.org/developer/diary.php?diary_user=2781
pgp0.pgp
Description: PGP signature
20 matches
Mail list logo
