Op donderdag 05 april 2001 01:43, schreef Per Bothner:
> Egon Willighagen <[EMAIL PROTECTED]> writes:
> > I like the idea of a Perl launcher...
>
> I hate the idea of requiring Perl in order to run Java ...
>
> Of course Debian can use whatever wrappers it will, but no Java
> application *I* manag
On 4 Apr 2001, Per Bothner wrote:
> Egon Willighagen <[EMAIL PROTECTED]> writes:
>
> > I like the idea of a Perl launcher...
>
> I hate the idea of requiring Perl in order to run Java ...
So gcj has jvgenmain. You can do the same for other VMs-- generate a
small executable that invokes the ma
>> The `L.so' in this case should probably follow the naming scheme we
>> adopted for the `.so' files that Class.forName will automatically try
>> to load. That will make it so that the linker and Class.forName will
>> agree -- it won't matter to the end program whether a class is loaded
>> at run
Egon Willighagen <[EMAIL PROTECTED]> writes:
> I like the idea of a Perl launcher...
I hate the idea of requiring Perl in order to run Java ...
Of course Debian can use whatever wrappers it will, but no Java
application *I* manage will require Perl to run.
--
--Per Bothner
[EMAIL PROTEC
Tom Tromey <[EMAIL PROTECTED]> writes:
> I think we'll need a way to disable the built-in search path except
> for libgcj.jar.
I'm concentrating on the default paths, for installed software.
We will need flags to override the builtin paths, for example
for building libgcj itself, or for building
On 4 Apr 2001, Per Bothner wrote:
> Egon Willighagen <[EMAIL PROTECTED]> writes:
>
> > I like the idea of a Perl launcher...
>
> I hate the idea of requiring Perl in order to run Java ...
So gcj has jvgenmain. You can do the same for other VMs-- generate a
small executable that invokes the m
>> The `L.so' in this case should probably follow the naming scheme we
>> adopted for the `.so' files that Class.forName will automatically try
>> to load. That will make it so that the linker and Class.forName will
>> agree -- it won't matter to the end program whether a class is loaded
>> at ru
Egon Willighagen <[EMAIL PROTECTED]> writes:
> I like the idea of a Perl launcher...
I hate the idea of requiring Perl in order to run Java ...
Of course Debian can use whatever wrappers it will, but no Java
application *I* manage will require Perl to run.
--
--Per Bothner
[EMAIL PROTE
Tom Tromey <[EMAIL PROTECTED]> writes:
> I think we'll need a way to disable the built-in search path except
> for libgcj.jar.
I'm concentrating on the default paths, for installed software.
We will need flags to override the builtin paths, for example
for building libgcj itself, or for building
> "Per" == Per Bothner <[EMAIL PROTECTED]> writes:
Per> So to summarize: The builtin search path should be (in this order):
Per> (1) each .jar file in /usr/share/java/$implementation
Per> (2) each .jar file in /usr/share/java
Per> (3) the /usr/share/java directory itself
I think we'll need a
> "Per" == Per Bothner <[EMAIL PROTECTED]> writes:
Per> So to summarize: The builtin search path should be (in this order):
Per> (1) each .jar file in /usr/share/java/$implementation
Per> (2) each .jar file in /usr/share/java
Per> (3) the /usr/share/java directory itself
I think we'll need
Op dinsdag 03 april 2001 18:49, schreef Paul Reavis:
> On 03 Apr 2001 07:50:33 +0200, Egon Willighagen wrote:
> > > I've left out versioning issues. If one want to support multiple
> > > versions of the same library one could install LIBRARY-VERSION.jar,
> > > and install a symlink from LIBRARY.ja
Op dinsdag 03 april 2001 19:00, schreef Per Bothner:
> > Or maybe, to have two conflicting packages program and program-gcj?
>
> I've concentrated on where things get installed, not so much on how
> things get split into package, but here are soem notes on the latter.
> For libraries it might be re
Hi,
the BTS still holds my ITP to package JPython (nowadays called Jython).
Jython is an implementation of the Python language in pure Java, see
http://www.jython.org/.
As much as I'm interested in the issues involved with a painless coexistence
of C-Python and Jython on Debian, I haven't really
Op dinsdag 03 april 2001 18:49, schreef Paul Reavis:
> On 03 Apr 2001 07:50:33 +0200, Egon Willighagen wrote:
> > > I've left out versioning issues. If one want to support multiple
> > > versions of the same library one could install LIBRARY-VERSION.jar,
> > > and install a symlink from LIBRARY.j
Op dinsdag 03 april 2001 19:00, schreef Per Bothner:
> > Or maybe, to have two conflicting packages program and program-gcj?
>
> I've concentrated on where things get installed, not so much on how
> things get split into package, but here are soem notes on the latter.
> For libraries it might be r
Hi,
the BTS still holds my ITP to package JPython (nowadays called Jython).
Jython is an implementation of the Python language in pure Java, see
http://www.jython.org/.
As much as I'm interested in the issues involved with a painless coexistence
of C-Python and Jython on Debian, I haven't really
17 matches
Mail list logo
