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

Re: java policy for debian, shared libraries...



Hi

On Sun, Sep 15, 2002 at 01:56:01PM +0200, Robert Olofsson wrote:
> Hello!
> 
> I read http://www.debian.org/doc/packaging-manuals/java-policy/
> There is one thing that I cant find covered by that policy.

Hmm ok.

> I currently develop jmp (http://www.khelekore.org/jmp/) a java profiler.
> Java profilers are written in C/C++ and compiled to shared libraries, 
> libjmp.so for jmp. Many profilers today have a java front end, jmp does 
> not (it uses a gtk front end).

What exactly is a java profiler? A java debugging utility?

> jmp is C code only.
> jmp is compiled by gcc.
> jmp has no binary (only libjmp.so is installed).
> libjmp.so should probably go into /usr/lib/ or someplace like that.

According to this it has nothing to do with java.

> jmp needs a jvm to run (java -Xrunjmp my.fine.Program). The jvm loads 
> the library with dlopen.

But this of course makes it java-related. Does it work with any jvm or
just some specific? Actually I do not think this has to be covered by the
java policy.

> The java debugger also has a similar interface but I am not aware of any 
> debugger that does not use any java classes.
> There probably exists more interfaces that use dynamic loading to do 
> strange stuff with the jvm....
> 
> Where to this fit in?

In the normal debian policy. We just have to make sure that the
java-policy excludes this possibility. I just checked and I do
not think it does.

Do you think something is needed in the policy?

Regards,

// Ola

> /robo
> 

PS. I cc:ed the debian-java@l.d.o list for suggestions.
DS.

-- 
 --------------------- Ola Lundqvist ---------------------------
/  opal@debian.org                     Annebergsslingan 37      \
|  opal@lysator.liu.se                 654 65 KARLSTAD          |
|  +46 (0)54-10 14 30                  +46 (0)70-332 1551       |
|  http://www.opal.dhs.org             UIN/icq: 4912500         |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---------------------------------------------------------------



Reply to: