Bug 441

Summary:	Please rename jogl & gluegen files
Product:	Default	Reporter:	Sylvestre Ledru <sylvestre>
Component:	default	Assignee:	Sven Gothel <sgothel>
Status:	VERIFIED WONTFIX
Severity:	blocker	CC:	sylvestre
Priority:	---
Version:	unspecified
Hardware:	All
OS:	all
Type:	---	SCM Refs:
Workaround:	---

Description Sylvestre Ledru 2010-12-04 09:36:23 CET

Hello,

I am starting to package jogl 2 & gluegen 2 into Debian.
Since version 1 & 2 are not compatible, I will have to leave the two packages coexisting together.

I would like to propose you to rename jogl*.jar to jogl2*.jar (idem for the native lib) and also gluegen*.jar to gluegen2*.jar.

It is very important for packaging purposes to separate these two versions.

Thanks for considering this!

Comment 1 Sven Gothel 2010-12-06 17:38:19 CET

Sorry Sylvestre,

our deployment scheme doesn't require to change JAR names for each version,
we also no more support prev. JOGL versions anyway.

However, if you are kind and create Debian 'snapshot' packages,
you always can give them some specific name marking them as
non compatible, hence you have to install either one .. AFAIK.

In little time, at least after we have released 2.0-final,
JOGL 1.1 legacy shouldn't matter anymore anyways.

Cheers, Sven

Comment 2 Sylvestre Ledru 2010-12-06 23:56:18 CET

(In reply to comment #1)
> Sorry Sylvestre,
> 
> our deployment scheme doesn't require to change JAR names for each version,
> we also no more support prev. JOGL versions anyway.
At least for a major release which contains many API changes.
I am not asking for every release.
What I have done for now is to rename gluegen-rt.jar to gluegen2-rt.jar and libgluegen-rt.so to libgluegen2-rt.so
This allow the installation of both jogl 1.1 & 2.0.

> However, if you are kind and create Debian 'snapshot' packages,
> you always can give them some specific name marking them as
> non compatible, hence you have to install either one .. AFAIK.
Well, I don't see the gain for users to have them conflicting with either others since both versions could coexist one with the other.

> In little time, at least after we have released 2.0-final,
> JOGL 1.1 legacy shouldn't matter anymore anyways.
We have to wait software to be ported to version 2.0 in the distribution to remove jogl 1.1... and this could take a while.
For example, I have no idea when Worldwind could be ported to JoGL 2.0...

Anyway, thanks for the answer