Re: [Cooker] Packaging Java class libraries

2001-07-09 Thread David Walluck
Guillaume Rousse wrote: > Corrected now. You can subscribe by going there > http://sourceforge.net/projects/jpackage, as well as look as the reply from Do I have to use the sourceforge page or can I send some subscribe message to this list. If so, how? > I find definitly more easy to const

Re: [Cooker] Packaging Java class libraries

2001-07-09 Thread Edward Avis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 9 Jul 2001, Guillaume Rousse wrote: [[EMAIL PROTECTED]] >You can subscribe by going there http://sourceforge.net/projects/jpackage, I've subscribed. Future messages on this subject will go only to that list. For real this time :-). >as w

Re: [Cooker] Packaging Java class libraries

2001-07-09 Thread Guillaume Rousse
Ainsi parlait Edward Avis : > >Sorry, it is yet a private list. I'm asking my other fellow to open it, so > >stay on cooker for now. > Okay, I'll stay on this list. Please ignore the Reply-To header in my > previous message :-). Corrected now. You can subscribe by going there http://sourceforge.

Re: [Cooker] Packaging Java class libraries

2001-07-09 Thread Edward Avis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 9 Jul 2001, Guillaume Rousse wrote: >>>(http://jpackage.sourceforge.net/packages.php) >> >>I can't download anything from there via anonymous FTP, is it not public >>yet? > >I just tried jpackage.sourceforge.net/pub/jpackage, everything seems

Re: [Cooker] Packaging Java class libraries

2001-07-09 Thread Guillaume Rousse
Ainsi parlait Edward Avis : > On Mon, 9 Jul 2001, Guillaume Rousse wrote: > >and jpackage project (http://jpackage.sourceforge.net), > > I see that the website doesn't have much content yet. Use rpm index page instead (http://jpackage.sourceforge.net/packages.php) On my own local mirror, it weighs

Re: [Cooker] Packaging Java class libraries

2001-07-09 Thread Edward Avis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 9 Jul 2001, Guillaume Rousse wrote: >There are already several existing java packaging project. See RPMS for java >development (http://freshmeat.net/projects/rpms4java/), They seem to store .jar files straight in /usr/share/java/. Each RPM

Re: [Cooker] Packaging Java class libraries

2001-07-09 Thread Guillaume Rousse
Sorry for catching this thread lately. There are already several existing java packaging project. See RPMS for java development (http://freshmeat.net/projects/rpms4java/), recentely announced on sourceforge, and jpackage project (http://jpackage.sourceforge.net), which wasn't publicy announced

Re: [Cooker] Packaging Java class libraries

2001-07-09 Thread Edward Avis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 9 Jul 2001, Frank Meurer wrote: >>Maybe say that we should add: >> >>- - /usr/share/java/*.jar >>- - /usr/share/java/classes/* >> >>to the CLASSPATH. > >Yes, that looks fine! Should first check what other distributions do. >Maybe a switched

Re: [Cooker] Packaging Java class libraries

2001-07-09 Thread Frank Meurer
In Mon, 9 Jul 2001, Edward Avis cum veritate scripsit : [...] > If you think that /usr/share/java/ might be used for stuff other than > compiled Java classes, then create a subdirectory > /usr/share/java/classes/ and add the contents of that to CLASSPATH. > Although this conflicts with what some

Re: [Cooker] Packaging Java class libraries

2001-07-09 Thread Edward Avis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 8 Jul 2001, Axalon wrote: [Java] >Precedence set by Kaffe pkg, which is atleast in theory compliant with the >standard. /usr/java should be broke apart into /usr/lib, /usr/bin, and >/usr/share/"name". I agree, but try telling Sun that :-P.

Re: [Cooker] Packaging Java class libraries

2001-07-09 Thread Edward Avis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 8 Jul 2001, David Walluck wrote: >>I propose that Java libraries be installed under >>/usr/share/java/, either as .jar files or as subdirectories full of >>.class files. And /etc/profile.d/java should do something like: >> >>for i in /usr/sh

Re: [Cooker] Packaging Java class libraries

2001-07-08 Thread David Walluck
On Sun, 8 Jul 2001, Axalon wrote: > Precedence set by Kaffe pkg, which is atleast in theory compliant with the > standard. /usr/java should be broke apart into /usr/lib, /usr/bin, and > /usr/share/"name". "Global libs" (for lack of knowledge?) would get > installed into the generic CLASSPATH > (

Re: [Cooker] Packaging Java class libraries

2001-07-08 Thread Frank Meurer
In Sun, 8 Jul 2001, David Walluck cum veritate scripsit : > On Sun, 8 Jul 2001, Edward Avis wrote: [...] > do not seem to have an official stance on Java support. There are no java > rpms in Cooker. for example. IMHO the licenses of the Blackdown port should allow to integrate it. > Problem i

Re: [Cooker] Packaging Java class libraries

2001-07-08 Thread Axalon
On Sun, 8 Jul 2001, David Walluck wrote: > On Sun, 8 Jul 2001, Edward Avis wrote: > > > If not, I propose that Java libraries be installed under > > /usr/share/java/, either as .jar files or as subdirectories full of > > .class files. And /etc/profile.d/java should do something like: > > > > fo

Re: [Cooker] Packaging Java class libraries

2001-07-08 Thread David Walluck
On Sun, 8 Jul 2001, Edward Avis wrote: > If not, I propose that Java libraries be installed under > /usr/share/java/, either as .jar files or as subdirectories full of > .class files. And /etc/profile.d/java should do something like: > > for i in /usr/share/java/*; do > export CLASSPATH=$CLA

Re: [Cooker] Packaging Java class libraries

2001-07-08 Thread Edward Avis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 8 Jul 2001, michael wrote: >>What is the convention for RPMs of compiled Java libraries? >Would this solve the problem with Konqueror and Java issues? Probably not. We're discussing adding new libraries of Java code to the system, and wher

Re: [Cooker] Packaging Java class libraries

2001-07-08 Thread michael
Edward Avis wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > What is the convention for RPMs of compiled Java libraries? > > Would this solve the problem with Konqueror and Java issues? Or has it been solved w/o me finding out? -michael- -- Science is built up with facts, as a

Re: [Cooker] Packaging Java class libraries

2001-07-08 Thread Frank Meurer
In Sun, 8 Jul 2001, Edward Avis cum veritate scripsit : > >Actually they WILL clash! > > Huh? Yeah! ;-) > import com.snakeoil.palisade.*; > > or > > import com.gerbil-gratings.simphoni.*; > > There's no problem unless you mix the two. Example: My Program uses LIBOLD (com.firm.lib) and I also

Re: [Cooker] Packaging Java class libraries

2001-07-08 Thread Edward Avis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 8 Jul 2001, Frank Meurer wrote: [Java] >>A library from one vendor will have classes called >> >>com.snakeoil.palisade.Whatever >> >>and another vendor will use >> >>com.gerbil-gratings.simphoni.Whatever >> > so they can't clash. >Actually

Re: [Cooker] Packaging Java class libraries

2001-07-08 Thread Frank Meurer
In Sun, 8 Jul 2001, Edward Avis cum veritate scripsit : [...] > >>for i in /usr/share/java/*; do > >>export CLASSPATH=$CLASSPATH:$i > >>done > > >But... maybe there will be (with a /huge/ growing number of jars etc.) > >some broken dependencies or conflicts due to the wrong sequence of jars

Re: [Cooker] Packaging Java class libraries

2001-07-08 Thread Edward Avis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 8 Jul 2001, Frank Meurer wrote: [installing Java library .jar files] >>Sun sometimes recommend that you install new .jar files in >>/usr/java/jre/lib/ or /usr/java/jre/lib/ext/. Then they get picked up >>automatically without needing to be

Re: [Cooker] Packaging Java class libraries

2001-07-08 Thread Frank Meurer
On Sun, 8 Jul 2001, Edward Avis cum veritate scripsit : > I have my .bashrc set up to do this automatically for every file in a > certain directory. It would be possible to add a new script in > /etc/profile.d/ to do this. I install 3rd party jars in a shared directory (NFS) and change/add my

[Cooker] Packaging Java class libraries

2001-07-08 Thread Edward Avis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What is the convention for RPMs of compiled Java libraries? Some packages put the code into a .jar file and install this under /usr/share/java. Then I think it is up to the user to make sure that the file is included in CLASSPATH, eg: % export CLAS