On Tue, 19 Aug 2003 15:59:33 +0200
Stefan Gybas <[EMAIL PROTECTED]> wrote:
> Arnaud Vandyck wrote:
>
> > Hi Stefan, I'm migrating my libgef-java to CBDS but I do not think you
> > did commit your changes to libcommons-beanutils-java to pkg-java on
> > Alioth? I'd like to see your
Arnaud Vandyck wrote:
Hi Stefan, I'm migrating my libgef-java to CBDS but I do not think you
did commit your changes to libcommons-beanutils-java to pkg-java on
Alioth? I'd like to see your complete debian/rules and you
debian/control files.
No, I did not commit the changes, s
On Thu, 14 Aug 2003 22:27:05 +0200
Stefan Gybas <[EMAIL PROTECTED]> wrote:
[...]
> If you are maintaining a package which uses Ant please test the new
> build system and send me feedback. I'll submit the two files to the CDBS
> authors if I don't receive any compaints or suggestions for major
On Tue, 19 Aug 2003 15:59:33 +0200
Stefan Gybas <[EMAIL PROTECTED]> wrote:
> Arnaud Vandyck wrote:
>
> > Hi Stefan, I'm migrating my libgef-java to CBDS but I do not think you
> > did commit your changes to libcommons-beanutils-java to pkg-java on
> > Alioth? I'd like to see your
Arnaud Vandyck wrote:
Hi Stefan, I'm migrating my libgef-java to CBDS but I do not think you
did commit your changes to libcommons-beanutils-java to pkg-java on
Alioth? I'd like to see your complete debian/rules and you
debian/control files.
No, I did not commit the changes,
On Thu, 14 Aug 2003 22:27:05 +0200
Stefan Gybas <[EMAIL PROTECTED]> wrote:
[...]
> If you are maintaining a package which uses Ant please test the new
> build system and send me feedback. I'll submit the two files to the CDBS
> authors if I don't receive any compaints or suggestions for major
Hello Arnaud,
Friday, August 15, 2003, 11:46:31 PM, you wrote:
> Jan Schulz <[EMAIL PROTECTED]> wrote:
>> IMO the big enchancement is, that you only have to specify the
>> Depends once: in debian/control and everything else is added from
>> there on.
> That's what we all want ;)
Ok, I take that a
Hello Arnaud,
Friday, August 15, 2003, 11:46:31 PM, you wrote:
> Jan Schulz <[EMAIL PROTECTED]> wrote:
>> IMO the big enchancement is, that you only have to specify the
>> Depends once: in debian/control and everything else is added from
>> there on.
> That's what we all want ;)
Ok, I take that a
Hi all
On Thu, 14 Aug 2003 21:39:17 +0200
Jan Schulz <[EMAIL PROTECTED]> wrote:
libxalan2-java depends on libxerces2-java but you do not need
xml-apis.jar AND xmlParserAPIs.jar in your classpath. It's up to
the maintainer of the application to know what to do.
This will anyway have to
On Thu, 14 Aug 2003 21:39:17 +0200
Jan Schulz <[EMAIL PROTECTED]> wrote:
[...]
> Usually you need to know what version of what lib you need. If that
> version is packages, you add this package name to your Depends:
> dh_java (or yourself, if thats not oncluded in such a script) will
> then add t
Hi all
On Thu, 14 Aug 2003 21:39:17 +0200
Jan Schulz <[EMAIL PROTECTED]> wrote:
libxalan2-java depends on libxerces2-java but you do not need
xml-apis.jar AND xmlParserAPIs.jar in your classpath. It's up to
the maintainer of the application to know what to do.
This will anyway have to
On Thu, 14 Aug 2003 21:39:17 +0200
Jan Schulz <[EMAIL PROTECTED]> wrote:
[...]
> Usually you need to know what version of what lib you need. If that
> version is packages, you add this package name to your Depends:
> dh_java (or yourself, if thats not oncluded in such a script) will
> then add t
Hallo Arnaud,
* Arnaud Vandyck wrote:
>Can you give me some more explanations (private or on the list).
Here we go... I think you ar eon the list, so no private reply.
>> * Jan Schulz wrote:
>> ** getclasspath.sh
This script will be used in any java applications startscript. You (or
a dh_java)
Ross Burton wrote:
Excellent plan. CDBS is a godsend for packaging GNOME software (2
includes).
I think it is now also for Ant-based java software. :-) Attached is the
first version of ant.mk and ant-vars.mk for CDBS. I have tested it with
some packages, for example debian/rules for Commons Bean
Hello Arnaud,
Thursday, August 14, 2003, 3:33:46 PM, you wrote:
>> >> * Jan Schulz wrote:
>> >> ** getclasspath.sh
>>
>> This script will be used in any java applications startscript. You (or
>> a dh_java) put the dependencies (package names) as param and it will
>> give you the complete classp
Hello Arnaud,
Thursday, August 14, 2003, 3:33:46 PM, you wrote:
>> >> * Jan Schulz wrote:
>> >> ** getclasspath.sh
>>
>> This script will be used in any java applications startscript. You (or
>> a dh_java) put the dependencies (package names) as param and it will
>> give you the complete classp
On Sun, 10 Aug 2003 20:10:45 +0200
Jan Schulz <[EMAIL PROTECTED]> wrote:
> Hallo Arnaud,
Hallo Jan,
> * Arnaud Vandyck wrote:
> > Can you give me some more explanations (private or on the list).
> Here we go... I think you are on the list, so no private reply.
Yes I'm on the list and told you
Hallo Jan,
* Jan Schulz wrote:
>For the infrastructure: This shouldn't be the problem: We don't have
>to deal with 'runtime' loading, just with adding something 'shortly
>before runtime'. Plugins should be done anyway with seperate dirs and
>classloader (that's at least my experience with eclipse,
On Sun, 10 Aug 2003 20:10:45 +0200
Jan Schulz <[EMAIL PROTECTED]> wrote:
> Hallo Arnaud,
Hallo Jan,
> * Arnaud Vandyck wrote:
> > Can you give me some more explanations (private or on the list).
> Here we go... I think you are on the list, so no private reply.
Yes I'm on the list and told you
Hallo Arnaud,
* Arnaud Vandyck wrote:
>Can you give me some more explanations (private or on the list).
Here we go... I think you ar eon the list, so no private reply.
>> * Jan Schulz wrote:
>> ** getclasspath.sh
This script will be used in any java applications startscript. You (or
a dh_java)
Hallo Jan,
* Jan Schulz wrote:
>For the infrastructure: This shouldn't be the problem: We don't have
>to deal with 'runtime' loading, just with adding something 'shortly
>before runtime'. Plugins should be done anyway with seperate dirs and
>classloader (that's at least my experience with eclipse,
Hallo Andrew,
* Andrew Pimlott wrote:
>If nothing else, you could put a variable
>FORCE_OFFICIAL_BUILD_DEPENDENCIES=1 at the top of debian/rules, and
>let people unset it. It would be nice if something like this became
>standard for all packages.
How is that actually handled on the buildd maschi
On Tue, Jul 29, 2003 at 03:45:08PM +0200, Stefan Gybas wrote:
> Andrew Pimlott wrote:
>
> >You might want official builds to always use the same compiler, but
> >there's no reason not to make it convenient for others to use their
> >preferred compiler. Especially when the preferred compiler is
>
On Tue, Jul 29, 2003 at 08:23:23PM +0200, Stefan Gybas wrote:
> It is just for building the package. I don't think that most users will
> rebuild the Java packages, especially since they are architecture
> independent. You also need a lot of -dev packages (and gcc) for
> rebuilding C and C++ pac
Hallo Andrew,
* Andrew Pimlott wrote:
>If nothing else, you could put a variable
>FORCE_OFFICIAL_BUILD_DEPENDENCIES=1 at the top of debian/rules, and
>let people unset it. It would be nice if something like this became
>standard for all packages.
How is that actually handled on the buildd maschi
On Tue, Jul 29, 2003 at 03:45:08PM +0200, Stefan Gybas wrote:
> Andrew Pimlott wrote:
>
> >You might want official builds to always use the same compiler, but
> >there's no reason not to make it convenient for others to use their
> >preferred compiler. Especially when the preferred compiler is
>
On Tue, Jul 29, 2003 at 08:23:23PM +0200, Stefan Gybas wrote:
> It is just for building the package. I don't think that most users will
> rebuild the Java packages, especially since they are architecture
> independent. You also need a lot of -dev packages (and gcc) for
> rebuilding C and C++ pac
Stefan Gybas <[EMAIL PROTECTED]> wrote:
> Jan Schulz wrote:
>
> > I'm currently using this line to get 'java' in debian/rules:
> > jdk_dirs=/usr/lib/j2sdk1.4 /usr/lib/j2se/1.4 /usr/lib/j2se/1.3
> > /usr/lib/j2sdk1.3
> > JAVA_HOME ?= $(shell for jdir in $(jdk_dirs) ; do if [ -d "$$jdir" ]; \
> > t
Stefan Gybas <[EMAIL PROTECTED]> wrote:
> Jan Schulz wrote:
>
> > I'm currently using this line to get 'java' in debian/rules:
> > jdk_dirs=/usr/lib/j2sdk1.4 /usr/lib/j2se/1.4 /usr/lib/j2se/1.3 /usr/lib/j2sdk1.3
> > JAVA_HOME ?= $(shell for jdir in $(jdk_dirs) ; do if [ -d "$$jdir" ]; \
> > then e
Hallo Stefan,
* Stefan Gybas wrote:
>You are a package manager, not a "standard" user. You should have a lot
>of differnt JDK installed anyway to be ably to very bug reports so
>what's the problem with on specific JDK in build dependencies?
Almost half of the bugs/mails about eclipse ended in t
Hallo Stefan,
* Stefan Gybas wrote:
>You are a package manager, not a "standard" user. You should have a lot
>of differnt JDK installed anyway to be ably to very bug reports so
>what's the problem with on specific JDK in build dependencies?
Almost half of the bugs/mails about eclipse ended in t
Jan Schulz wrote:
I'm doing it all the time: I'm running woody and I have specified
deb ... stable
deb-src ... unstable
You are a package manager, not a "standard" user. You should have a lot
of differnt JDK installed anyway to be ably to very bug reports so
what's the problem with on specific JD
Hallo Stefan,
* Stefan Gybas wrote:
>>I've had a look at this bug and I thing we should not fource a
>>specific javac or java at our users. If they don't want to download a
>>BD JDK, then this should be made possible.
>It is just for building the package. I don't think that most users will
>rebui
Jan Schulz wrote:
I've had a look at this bug and I thing we should not fource a
specific javac or java at our users. If they don't want to download a
BD JDK, then this should be made possible.
It is just for building the package. I don't think that most users will
rebuild the Java packages, espec
Jan Schulz wrote:
I'm doing it all the time: I'm running woody and I have specified
deb ... stable
deb-src ... unstable
You are a package manager, not a "standard" user. You should have a lot
of differnt JDK installed anyway to be ably to very bug reports so
what's the problem with on specific J
Hallo Stefan,
* Stefan Gybas wrote:
>>Excellent! ;) Can I copy/paste it in mine? ;)
I've also just inherited this code... :)
>I've written this code 2 years ago when Blackdown changed their
>JAVA_HOME in the j2sdk1.3 packages from /usr/lib/j2sdk1.3 to
>/usr/lib/j2se/1.3 so packages could be bu
Hallo Stefan,
* Stefan Gybas wrote:
>>I've had a look at this bug and I thing we should not fource a
>>specific javac or java at our users. If they don't want to download a
>>BD JDK, then this should be made possible.
>It is just for building the package. I don't think that most users will
>rebui
Hallo Stefan,
* Stefan Gybas wrote:
>Jan Schulz wrote:
>In eclipse? I think #197484 is a perfect example why this is bad and why
>you should use one specific JDK version.
Yep, that one was bad. But I don't think that I want to install a
specific JDK just for compiling. OK, I've curently 5 JDKs i
Arnaud Vandyck wrote:
Excellent! ;) Can I copy/paste it in mine? ;)
No, please don't!
I've written this code 2 years ago when Blackdown changed their
JAVA_HOME in the j2sdk1.3 packages from /usr/lib/j2sdk1.3 to
/usr/lib/j2se/1.3 so packages could be build with both versions (see
#122584). It ist
Jan Schulz wrote:
I've had a look at this bug and I thing we should not fource a
specific javac or java at our users. If they don't want to download a
BD JDK, then this should be made possible.
It is just for building the package. I don't think that most users will
rebuild the Java packages, espe
Jan Schulz wrote:
I'm currently using this line to get 'java' in debian/rules:
jdk_dirs=/usr/lib/j2sdk1.4 /usr/lib/j2se/1.4 /usr/lib/j2se/1.3 /usr/lib/j2sdk1.3
JAVA_HOME ?= $(shell for jdir in $(jdk_dirs) ; do if [ -d "$$jdir" ]; \
then echo \
$$jdir;exit 0;fi;done)
In eclipse? I think #197484 is a
Jan Schulz <[EMAIL PROTECTED]> wrote:
[...]
> I'm currently using this line to get 'java' in debian/rules:
> jdk_dirs=/usr/lib/j2sdk1.4 /usr/lib/j2se/1.4 /usr/lib/j2se/1.3
> /usr/lib/j2sdk1.3
> JAVA_HOME ?= $(shell for jdir in $(jdk_dirs) ; do if [ -d "$$jdir" ]; \
> then echo \
> $$jdir;exit 0;fi
Hallo Stefan,
* Stefan Gybas wrote:
>>Excellent! ;) Can I copy/paste it in mine? ;)
I've also just inherited this code... :)
>I've written this code 2 years ago when Blackdown changed their
>JAVA_HOME in the j2sdk1.3 packages from /usr/lib/j2sdk1.3 to
>/usr/lib/j2se/1.3 so packages could be bu
Hallo Arnaud,
* Arnaud Vandyck wrote:
>Stefan Gybas <[EMAIL PROTECTED]> wrote:
>What are the possible values of JAVA_HOME where you want to use
>something different from Blackdown's or Sun's JDK?
There are a lot IMO:
The values, where mpkg-j2sdk puts the JDKs, /usr/local... and so on.
I
Hallo Stefan,
* Stefan Gybas wrote:
>Jan Schulz wrote:
>In eclipse? I think #197484 is a perfect example why this is bad and why
>you should use one specific JDK version.
Yep, that one was bad. But I don't think that I want to install a
specific JDK just for compiling. OK, I've curently 5 JDKs i
Arnaud Vandyck wrote:
Excellent! ;) Can I copy/paste it in mine? ;)
No, please don't!
I've written this code 2 years ago when Blackdown changed their
JAVA_HOME in the j2sdk1.3 packages from /usr/lib/j2sdk1.3 to
/usr/lib/j2se/1.3 so packages could be build with both versions (see
#122584). It i
Jan Schulz wrote:
I'm currently using this line to get 'java' in debian/rules:
jdk_dirs=/usr/lib/j2sdk1.4 /usr/lib/j2se/1.4 /usr/lib/j2se/1.3 /usr/lib/j2sdk1.3
JAVA_HOME ?= $(shell for jdir in $(jdk_dirs) ; do if [ -d "$$jdir" ]; \
then echo \
$$jdir;exit 0;fi;done)
In eclipse? I think #197484 is
Jan Schulz <[EMAIL PROTECTED]> wrote:
[...]
> I'm currently using this line to get 'java' in debian/rules:
> jdk_dirs=/usr/lib/j2sdk1.4 /usr/lib/j2se/1.4 /usr/lib/j2se/1.3 /usr/lib/j2sdk1.3
> JAVA_HOME ?= $(shell for jdir in $(jdk_dirs) ; do if [ -d "$$jdir" ]; \
> then echo \
> $$jdir;exit 0;fi;do
Hallo Arnaud,
* Arnaud Vandyck wrote:
>Stefan Gybas <[EMAIL PROTECTED]> wrote:
>What are the possible values of JAVA_HOME where you want to use
>something different from Blackdown's or Sun's JDK?
There are a lot IMO:
The values, where mpkg-j2sdk puts the JDKs, /usr/local... and so on.
I
Andrew Pimlott wrote:
You might want official builds to always use the same compiler, but
there's no reason not to make it convenient for others to use their
preferred compiler. Especially when the preferred compiler is
proprietary. We should be moving away from hard-coding knowledge
about the co
On Mon, Jul 28, 2003 at 07:13:47PM +0200, Stefan Gybas wrote:
> That's exactly the purpose. A build dependency for a JVM should be
> specific, see http://pkg-java.alioth.debian.org/building.html for the
> reasons.
You might want official builds to always use the same compiler, but
there's no rea
Andrew Pimlott wrote:
You might want official builds to always use the same compiler, but
there's no reason not to make it convenient for others to use their
preferred compiler. Especially when the preferred compiler is
proprietary. We should be moving away from hard-coding knowledge
about the c
On Mon, Jul 28, 2003 at 07:13:47PM +0200, Stefan Gybas wrote:
> That's exactly the purpose. A build dependency for a JVM should be
> specific, see http://pkg-java.alioth.debian.org/building.html for the
> reasons.
You might want official builds to always use the same compiler, but
there's no rea
Stefan Gybas <[EMAIL PROTECTED]> wrote:
> Daniel Bonniot wrote:
> > It's best to have both options. Otherwise it forces every package to
> > build-depend on a specific JVM, even though some might work with any
> > JVM.
>
> That's exactly the purpose. A build dependency for a JVM should be
> sp
Stefan Gybas <[EMAIL PROTECTED]> wrote:
> Daniel Bonniot wrote:
> > It's best to have both options. Otherwise it forces every package to
> > build-depend on a specific JVM, even though some might work with any
> > JVM.
>
> That's exactly the purpose. A build dependency for a JVM should be
> sp
On Mon, 28 Jul 2003 14:47:35 +0200, Stefan Gybas wrote:
>> I'd propose to conform to dh_* and use something like debian/ant or
>> debian/package.ant
>
> I think I have a better solution. I'd like to create an Ant class for CDBS
I want both!
Seriously, there are some cases where a full cdbs clas
Daniel Bonniot wrote:
It's best to have both options. Otherwise it forces every package to
build-depend on a specific JVM, even though some might work with any JVM.
That's exactly the purpose. A build dependency for a JVM should be
specific, see http://pkg-java.alioth.debian.org/building.html for
Jan Schulz wrote:
I don't agree, at least until this can also be done with packages,
where I have to call differnt targets, install difeferently and so on.
You can do this, just add the additional required commands to the
corresponding targets in debian/rules, like I did in doc++:
--- cut here ---
Ben Burton wrote:
JAVA_HOME=/usr/lib/j2se/1.4
Would there be a way of making this bit magic? i.e. following the
/usr/bin/java symlink?
This is dangerous - even if you jave j2sdk1.4 installed, /usr/bin/java
might still point to kaffe, gij, etc. I'd stick with a hard-coded path,
especia
Ross Burton wrote:
Excellent plan. CDBS is a godsend for packaging GNOME software (2
includes).
I must note here that the initial idea for a CDBS Ant class was from
Mark Howard, so he deserves most of the credits. I didn't even know what
CDBS was until he told me. :-)
Stefan
Hallo Stefan,
* Stefan Gybas wrote:
>I think I have a better solution. I'd like to create an Ant class for
>CDBS (http://build-common.alioth.debian.org/) so debian/rules will
>become really simple. For example, take a look at debian/rules from the
>latest doc++ package, it's really amazing. Ima
Hallo Arnaud,
* Arnaud Vandyck wrote:
>I'd propose to conform to dh_* and use something like
+1
>debian/ant or
>debian/package.ant
I don't think that a package.ant will be usefull: In eclipse, I have
two buildfiles (one patched, one "patched into existence"), which I
call tree times each (as t
> > JAVA_HOME=/usr/lib/j2se/1.4
>
> Would there be a way of making this bit magic? i.e. following the
> /usr/bin/java symlink?
This is dangerous - even if you jave j2sdk1.4 installed, /usr/bin/java
might still point to kaffe, gij, etc. I'd stick with a hard-coded path,
especially if it require
On Mon, 2003-07-28 at 13:47, Stefan Gybas wrote:
> Arnaud Vandyck wrote:
>
> > I'd propose to conform to dh_* and use something like
> > debian/ant or
> > debian/package.ant
>
> I think I have a better solution. I'd like to create an Ant class for
> CDBS (http://build-common.alioth.debian.org/)
On Mon, 28 Jul 2003 14:47:35 +0200, Stefan Gybas wrote:
>> I'd propose to conform to dh_* and use something like debian/ant or
>> debian/package.ant
>
> I think I have a better solution. I'd like to create an Ant class for CDBS
I want both!
Seriously, there are some cases where a full cdbs clas
Daniel Bonniot wrote:
It's best to have both options. Otherwise it forces every package to
build-depend on a specific JVM, even though some might work with any JVM.
That's exactly the purpose. A build dependency for a JVM should be
specific, see http://pkg-java.alioth.debian.org/building.html for
Jan Schulz wrote:
I don't agree, at least until this can also be done with packages,
where I have to call differnt targets, install difeferently and so on.
You can do this, just add the additional required commands to the
corresponding targets in debian/rules, like I did in doc++:
--- cut here ---
Ben Burton wrote:
JAVA_HOME=/usr/lib/j2se/1.4
Would there be a way of making this bit magic? i.e. following the
/usr/bin/java symlink?
This is dangerous - even if you jave j2sdk1.4 installed, /usr/bin/java
might still point to kaffe, gij, etc. I'd stick with a hard-coded path,
especi
Ross Burton wrote:
Excellent plan. CDBS is a godsend for packaging GNOME software (2
includes).
I must note here that the initial idea for a CDBS Ant class was from
Mark Howard, so he deserves most of the credits. I didn't even know what
CDBS was until he told me. :-)
Stefan
--
To UNSUBSCRIBE
Hallo Stefan,
* Stefan Gybas wrote:
>I think I have a better solution. I'd like to create an Ant class for
>CDBS (http://build-common.alioth.debian.org/) so debian/rules will
>become really simple. For example, take a look at debian/rules from the
>latest doc++ package, it's really amazing. Ima
Hallo Arnaud,
* Arnaud Vandyck wrote:
>I'd propose to conform to dh_* and use something like
+1
>debian/ant or
>debian/package.ant
I don't think that a package.ant will be usefull: In eclipse, I have
two buildfiles (one patched, one "patched into existence"), which I
call tree times each (as t
> > JAVA_HOME=/usr/lib/j2se/1.4
>
> Would there be a way of making this bit magic? i.e. following the
> /usr/bin/java symlink?
This is dangerous - even if you jave j2sdk1.4 installed, /usr/bin/java
might still point to kaffe, gij, etc. I'd stick with a hard-coded path,
especially if it require
On Mon, 2003-07-28 at 13:47, Stefan Gybas wrote:
> Arnaud Vandyck wrote:
>
> > I'd propose to conform to dh_* and use something like
> > debian/ant or
> > debian/package.ant
>
> I think I have a better solution. I'd like to create an Ant class for
> CDBS (http://build-common.alioth.debian.org/)
Arnaud Vandyck wrote:
I'd propose to conform to dh_* and use something like
debian/ant or
debian/package.ant
I think I have a better solution. I'd like to create an Ant class for
CDBS (http://build-common.alioth.debian.org/) so debian/rules will
become really simple. For example, take a look at
Arnaud Vandyck wrote:
I'd propose to conform to dh_* and use something like
debian/ant or
debian/package.ant
I think I have a better solution. I'd like to create an Ant class for
CDBS (http://build-common.alioth.debian.org/) so debian/rules will
become really simple. For example, take a look at
75 matches
Mail list logo
