On Wed, Oct 30, 2002 at 09:47:50AM +1100, Ben Burton wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
Hi
>
> Well that was fun, somebody unsubscribed me from debian-java; the first I
> heard was the successful unsubscription notification. As a result I nearly
> missed this. But an
On Tue, Oct 29, 2002 at 04:14:06PM -0600, Ean Schuessler wrote:
> I am attempting to resurrect both my Kaffe package and my involvement
> therein. This JVM registry seems like a great idea. What would it take
> to move it forward?
Well some development of a working format for the repository and to
On Wed, Oct 30, 2002 at 09:47:50AM +1100, Ben Burton wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
Hi
>
> Well that was fun, somebody unsubscribed me from debian-java; the first I
> heard was the successful unsubscription notification. As a result I nearly
> missed this. But an
On Tue, Oct 29, 2002 at 04:14:06PM -0600, Ean Schuessler wrote:
> I am attempting to resurrect both my Kaffe package and my involvement
> therein. This JVM registry seems like a great idea. What would it take
> to move it forward?
Well some development of a working format for the repository and to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well that was fun, somebody unsubscribed me from debian-java; the first I
heard was the successful unsubscription notification. As a result I nearly
missed this. But anyway:
> I am attempting to resurrect both my Kaffe package and my involvement
I am attempting to resurrect both my Kaffe package and my involvement
therein. This JVM registry seems like a great idea. What would it take
to move it forward?
On Fri, 2002-04-05 at 13:56, Ola Lundqvist wrote:
> > http://people.debian.org/~bab/javareg/
--
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well that was fun, somebody unsubscribed me from debian-java; the first I
heard was the successful unsubscription notification. As a result I nearly
missed this. But anyway:
> I am attempting to resurrect both my Kaffe package and my involvement
I am attempting to resurrect both my Kaffe package and my involvement
therein. This JVM registry seems like a great idea. What would it take
to move it forward?
On Fri, 2002-04-05 at 13:56, Ola Lundqvist wrote:
> > http://people.debian.org/~bab/javareg/
--
__
On Mon, Apr 01, 2002 at 09:19:13PM -0500, [EMAIL PROTECTED] wrote:
>
> So, kaffe would add an alternative of
> /wherever/kaffe/puts/Klasses.jar for (eg)
> /usr/share/java/bootclasses.jar . And jikes would take its
> bootclasspath (by default) from /usr/shar/java/bootclasses.jar.
> Using bootclass
On Sat, Apr 13, 2002 at 09:51:13PM +0200, Robert Bihlmeyer wrote:
> Robert Bihlmeyer <[EMAIL PROTECTED]> writes:
>
> > Oh, you don't seem to know the path from the top of your head! Me
> > neither. That's the point of jikes-kaffe: relieving you from having to
> > remember the obscure bootclasses p
On Mon, Apr 01, 2002 at 09:19:13PM -0500, [EMAIL PROTECTED] wrote:
>
> So, kaffe would add an alternative of
> /wherever/kaffe/puts/Klasses.jar for (eg)
> /usr/share/java/bootclasses.jar . And jikes would take its
> bootclasspath (by default) from /usr/shar/java/bootclasses.jar.
> Using bootclas
On Sat, Apr 13, 2002 at 09:51:13PM +0200, Robert Bihlmeyer wrote:
> Robert Bihlmeyer <[EMAIL PROTECTED]> writes:
>
> > Oh, you don't seem to know the path from the top of your head! Me
> > neither. That's the point of jikes-kaffe: relieving you from having to
> > remember the obscure bootclasses
Robert Bihlmeyer <[EMAIL PROTECTED]> writes:
> Oh, you don't seem to know the path from the top of your head! Me
> neither. That's the point of jikes-kaffe: relieving you from having to
> remember the obscure bootclasses path(s).
Especially since the new kaffe upload removed
/usr/share/kaffe/Klas
Robert Bihlmeyer <[EMAIL PROTECTED]> writes:
> Oh, you don't seem to know the path from the top of your head! Me
> neither. That's the point of jikes-kaffe: relieving you from having to
> remember the obscure bootclasses path(s).
Especially since the new kaffe upload removed
/usr/share/kaffe/Kla
On Thu, Apr 04, 2002 at 02:23:25PM +1000, Ben Burton wrote:
>
> > This is exactly the Java registry idea that's been discussed here in
> > the past. Check the archives from the end of last year. You might
> > in particular see Ben Burton's message with subject "JVM Registry:
> > Implemented".
>
On Wed, Apr 03, 2002 at 05:31:53PM -0800, Joe Emenaker wrote:
>
> > I was just thinking of a simple way to set up my classpath so I made
> > this suggestion. But if it is not common to do somthing like that, then
> > I have to live with that. And maybe collecting all libs might not lead
> > to the
On Thu, Apr 04, 2002 at 02:23:25PM +1000, Ben Burton wrote:
>
> > This is exactly the Java registry idea that's been discussed here in
> > the past. Check the archives from the end of last year. You might
> > in particular see Ben Burton's message with subject "JVM Registry:
> > Implemented".
>
On Wed, Apr 03, 2002 at 05:31:53PM -0800, Joe Emenaker wrote:
>
> > I was just thinking of a simple way to set up my classpath so I made
> > this suggestion. But if it is not common to do somthing like that, then
> > I have to live with that. And maybe collecting all libs might not lead
> > to th
> This is exactly the Java registry idea that's been discussed here in
> the past. Check the archives from the end of last year. You might
> in particular see Ben Burton's message with subject "JVM Registry:
> Implemented".
>
> I believe most people think it's basically a good idea, but I'm not
> This is exactly the Java registry idea that's been discussed here in
> the past. Check the archives from the end of last year. You might
> in particular see Ben Burton's message with subject "JVM Registry:
> Implemented".
>
> I believe most people think it's basically a good idea, but I'm not
On Wed, Apr 03, 2002 at 05:19:29PM -0800, Joe Emenaker wrote:
> On a related note
This is exactly the Java registry idea that's been discussed here in
the past. Check the archives from the end of last year. You might
in particular see Ben Burton's message with subject "JVM Registry:
Impleme
> I was just thinking of a simple way to set up my classpath so I made
> this suggestion. But if it is not common to do somthing like that, then
> I have to live with that. And maybe collecting all libs might not lead
> to the expected result, because of combining libs in different versions
> with
> It would be nice to have debconf provide a list of suitable installed
> JVM's. It could also have another option to select the path of a non-deb
> JDK installation.
On a related note
After having just made some .debs for j2sdk1.4, jbuilder6, and jEdit, I had
to write a couple of startup sc
On Wed, Apr 03, 2002 at 05:19:29PM -0800, Joe Emenaker wrote:
> On a related note
This is exactly the Java registry idea that's been discussed here in
the past. Check the archives from the end of last year. You might
in particular see Ben Burton's message with subject "JVM Registry:
Implem
> I was just thinking of a simple way to set up my classpath so I made
> this suggestion. But if it is not common to do somthing like that, then
> I have to live with that. And maybe collecting all libs might not lead
> to the expected result, because of combining libs in different versions
> wit
> It would be nice to have debconf provide a list of suitable installed
> JVM's. It could also have another option to select the path of a non-deb
> JDK installation.
On a related note
After having just made some .debs for j2sdk1.4, jbuilder6, and jEdit, I had
to write a couple of startup s
Hi all.
I recognize this discussion from some discussions some time ago.
Then we discussed that every package that provides java classes should
define its CLASSPATH in some way. I'd really like to see this in action.
There are suggestions in http://bugs.debian.org/103420
I'll include it here for
Hi all.
I recognize this discussion from some discussions some time ago.
Then we discussed that every package that provides java classes should
define its CLASSPATH in some way. I'd really like to see this in action.
There are suggestions in http://bugs.debian.org/103420
I'll include it here fo
On Sun, Mar 31, 2002 at 02:13:32PM -0800, Stephen Zander wrote:
> > "Colin" == Colin Watson <[EMAIL PROTECTED]> writes:
> Colin> That sounds like it would work better with autobuilders,
> Colin> too - you could build-depend on jikes (>= foo), invoke
> Colin> jikes-kaffe, and expect
On Tue, Apr 02, 2002 at 08:43:55PM +0200, Robert Bihlmeyer wrote:
> [EMAIL PROTECTED] writes:
>
> > I also think the jikes-kaffe, etc proposals are silly: You should
> > be able to achieve the same with a simple "jikes -bootclasspath
> > /wherever/kaffe/puts/Klasses.jar".
>
> Oh, you don't seem
On Sun, Mar 31, 2002 at 02:13:32PM -0800, Stephen Zander wrote:
> > "Colin" == Colin Watson <[EMAIL PROTECTED]> writes:
> Colin> That sounds like it would work better with autobuilders,
> Colin> too - you could build-depend on jikes (>= foo), invoke
> Colin> jikes-kaffe, and expect
[EMAIL PROTECTED] writes:
> I also think the jikes-kaffe, etc proposals are silly: You should
> be able to achieve the same with a simple "jikes -bootclasspath
> /wherever/kaffe/puts/Klasses.jar".
Oh, you don't seem to know the path from the top of your head! Me
neither. That's the point of jike
On Tue, Apr 02, 2002 at 08:43:55PM +0200, Robert Bihlmeyer wrote:
> [EMAIL PROTECTED] writes:
>
> > I also think the jikes-kaffe, etc proposals are silly: You should
> > be able to achieve the same with a simple "jikes -bootclasspath
> > /wherever/kaffe/puts/Klasses.jar".
>
> Oh, you don't seem
[EMAIL PROTECTED] writes:
> I also think the jikes-kaffe, etc proposals are silly: You should
> be able to achieve the same with a simple "jikes -bootclasspath
> /wherever/kaffe/puts/Klasses.jar".
Oh, you don't seem to know the path from the top of your head! Me
neither. That's the point of jik
On Fri, Mar 29, 2002 at 09:59:28PM -0600, Adam Majer wrote:
> At this moment I am the maintainer for Jikes. The one thing that I
> do not like about the package is that it does not work out of the
> box without some intervention from the user. That is, CLASSPATH
> needs to be defined.
>
> The tro
On Fri, Mar 29, 2002 at 09:59:28PM -0600, Adam Majer wrote:
> At this moment I am the maintainer for Jikes. The one thing that I
> do not like about the package is that it does not work out of the
> box without some intervention from the user. That is, CLASSPATH
> needs to be defined.
>
> The tr
Stefan Rücker <[EMAIL PROTECTED]> writes:
> > Stefan Rücker <[EMAIL PROTECTED]> writes:
> > Indeed, but a compiler can't take all installed libs (some of which
> > may not be in Debian packages, or not even in publically-readable
> > locations) into account.
>
> But how can you compile your progr
Stefan Rücker <[EMAIL PROTECTED]> writes:
> > Stefan Rücker <[EMAIL PROTECTED]> writes:
> > Indeed, but a compiler can't take all installed libs (some of which
> > may not be in Debian packages, or not even in publically-readable
> > locations) into account.
>
> But how can you compile your prog
> "Colin" == Colin Watson <[EMAIL PROTECTED]> writes:
Colin> That sounds like it would work better with autobuilders,
Colin> too - you could build-depend on jikes (>= foo), invoke
Colin> jikes-kaffe, and expect it to work everywhere.
What he said
--
Stephen (jdk maintainer)
"A d
> "Colin" == Colin Watson <[EMAIL PROTECTED]> writes:
Colin> That sounds like it would work better with autobuilders,
Colin> too - you could build-depend on jikes (>= foo), invoke
Colin> jikes-kaffe, and expect it to work everywhere.
What he said
--
Stephen (jdk maintainer)
"A
On Sat, Mar 30, 2002 at 12:04:29PM +0100, Robert Bihlmeyer wrote:
> Another way is to provide small scripts jikes-kaffe, jikes-ibm,
> jikes-sun, etc. and make /usr/bin/jikes handled by
> update-alternatives. This would make it consistent with how
> /usr/bin/java is currently handled. (Perhaps the d
Hi Robert,
On Saturday 30 March 2002 12:10, Robert Bihlmeyer wrote:
> Stefan Rücker <[EMAIL PROTECTED]> writes:
> > [...] but then you have your compiler not running out of the box
> > because many people use a big variety of libs for their programs
> > (just think about xml or all the apache libs
Hi Adam,
> > Don't forget Blackdown.
>
> Which package is that?
There is no official package in debian but it could be found on blackdown
mirrors under .../java.blackdown.org/debian/dists/woody/non-free/binary-i386/
A list of mirrors can be found on:
http://www.blackdown.org/java-linux/mirrors
On Sat, Mar 30, 2002 at 12:04:29PM +0100, Robert Bihlmeyer wrote:
> Another way is to provide small scripts jikes-kaffe, jikes-ibm,
> jikes-sun, etc. and make /usr/bin/jikes handled by
> update-alternatives. This would make it consistent with how
> /usr/bin/java is currently handled. (Perhaps the
Hi Robert,
On Saturday 30 March 2002 12:10, Robert Bihlmeyer wrote:
> Stefan Rücker <[EMAIL PROTECTED]> writes:
> > [...] but then you have your compiler not running out of the box
> > because many people use a big variety of libs for their programs
> > (just think about xml or all the apache lib
Hi Adam,
> > Don't forget Blackdown.
>
> Which package is that?
There is no official package in debian but it could be found on blackdown
mirrors under .../java.blackdown.org/debian/dists/woody/non-free/binary-i386/
A list of mirrors can be found on:
http://www.blackdown.org/java-linux/mirror
Hi,
On Fri, Mar 29, 2002 at 09:59:28PM -0600, Adam Majer wrote:
>
> Debconf should be used to allow the user to select the priority
> of the classes that jikes should check for. IOW, something like
>
> [1] - Kaffe
> [2] - Other [admin enters path]
> [3] - IBM JDK
> [4] - Sun.
> etc...
>
> I loo
On Sat, Mar 30, 2002 at 08:12:09AM -0500, Jesse wrote:
> On Fri, 2002-03-29 at 22:59, Adam Majer wrote:
> > [1] - Kaffe
> > [2] - Other [admin enters path]
> > [3] - IBM JDK
> > [4] - Sun.
> > etc...
> >
>
> Don't forget Blackdown.
Which package is that?
> It would be nice to have debconf provi
Hi,
On Fri, Mar 29, 2002 at 09:59:28PM -0600, Adam Majer wrote:
>
> Debconf should be used to allow the user to select the priority
> of the classes that jikes should check for. IOW, something like
>
> [1] - Kaffe
> [2] - Other [admin enters path]
> [3] - IBM JDK
> [4] - Sun.
> etc...
>
> I lo
On Sat, Mar 30, 2002 at 08:12:09AM -0500, Jesse wrote:
> On Fri, 2002-03-29 at 22:59, Adam Majer wrote:
> > [1] - Kaffe
> > [2] - Other [admin enters path]
> > [3] - IBM JDK
> > [4] - Sun.
> > etc...
> >
>
> Don't forget Blackdown.
Which package is that?
> It would be nice to have debconf prov
On Fri, 2002-03-29 at 22:59, Adam Majer wrote:
> [1] - Kaffe
> [2] - Other [admin enters path]
> [3] - IBM JDK
> [4] - Sun.
> etc...
>
Don't forget Blackdown.
It would be nice to have debconf provide a list of suitable installed
JVM's. It could also have another option to select the path of a no
Stefan Rücker <[EMAIL PROTECTED]> writes:
> [...] but then you have your compiler not running out of the box
> because many people use a big variety of libs for their programs
> (just think about xml or all the apache libs).
Indeed, but a compiler can't take all installed libs (some of which
may
"Adam Majer" <[EMAIL PROTECTED]> writes:
> Debconf should be used to allow the user to select the priority
> of the classes that jikes should check for. IOW, something like
>
> [1] - Kaffe
> [2] - Other [admin enters path]
> [3] - IBM JDK
> [4] - Sun.
> etc...
Another way is to provide small scr
On Fri, 2002-03-29 at 22:59, Adam Majer wrote:
> [1] - Kaffe
> [2] - Other [admin enters path]
> [3] - IBM JDK
> [4] - Sun.
> etc...
>
Don't forget Blackdown.
It would be nice to have debconf provide a list of suitable installed
JVM's. It could also have another option to select the path of a n
Stefan Rücker <[EMAIL PROTECTED]> writes:
> [...] but then you have your compiler not running out of the box
> because many people use a big variety of libs for their programs
> (just think about xml or all the apache libs).
Indeed, but a compiler can't take all installed libs (some of which
may
"Adam Majer" <[EMAIL PROTECTED]> writes:
> Debconf should be used to allow the user to select the priority
> of the classes that jikes should check for. IOW, something like
>
> [1] - Kaffe
> [2] - Other [admin enters path]
> [3] - IBM JDK
> [4] - Sun.
> etc...
Another way is to provide small sc
Hi Adam,
well I think that initially only the bootclasspath and the classpath for the
main packages (java.**, javax.**, ...) should be specified by debconf. So
your suggestion [1] Kaffe ... is quit allright but then you have your
compiler not running out of the box because many people use a big
Hi all,
At this moment I am the maintainer for Jikes. The one thing that I
do not like about the package is that it does not work out of the
box without some intervention from the user. That is, CLASSPATH
needs to be defined.
The trouble is that I don't think it is up to me to decide which
java
Hi Adam,
well I think that initially only the bootclasspath and the classpath for the
main packages (java.**, javax.**, ...) should be specified by debconf. So
your suggestion [1] Kaffe ... is quit allright but then you have your
compiler not running out of the box because many people use a bi
Hi all,
At this moment I am the maintainer for Jikes. The one thing that I
do not like about the package is that it does not work out of the
box without some intervention from the user. That is, CLASSPATH
needs to be defined.
The trouble is that I don't think it is up to me to decide which
jav
60 matches
Mail list logo
