[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Java Policy.



On Sunday 12 May 2002 22:00, Andrew Pimlott wrote:
> On Sun, May 12, 2002 at 09:40:05PM +0200, Ola Lundqvist wrote:
> > I disagree on that class files should be placed in a -dev package for the
> > same reason as I want every jar file to be placed in /usr/share/java
> > (maybe with an exception for jvm:s). You should always be allowed
> > to use the classes for some other purpose than just for some
> > executable to run.
>
> Ok, then it is just a question of naming.  Say my foo library can be
> compiled to .class files and GCJ .so files.  One option is to
> package both in libfoo-java, which would be architecture specific.
> But if you want to split them into an architecture-specific and an
> architecture-independent package, what do you call them? libfoo-java
> and libfoo-gcj-java?

If it would be architecture specific it would be like stuff compiled from C.
Thus libfoo and not libfoo-gcj-java... 

However, if libfoo is taken already you have trouble; then you would have a 
name clash and libfoo-gcj might not be too bad...

Egon


-- 
To UNSUBSCRIBE, email to debian-java-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: