8:39 a.m.
Hi, gentlemen,
For
some time the inclusion of the software Scilab [1] in our repos has been barred
by various dependencies, which were being resolved with time. Currently, the biggest
reason we do not have this
software in our repos is that it relies in a software called JOGL [2].
The
big question here is that JOGL, in his turn, depends on other software called
Gluegen [3] and, more specifically, it depends on the **source tree** of
Gluegen, as explained in the instructions for build [4]:
"Step
5 - Check out the GlueGen source tree:
JOGL
GlueGen relies on the project to autogenerate most of the Java and JNI code for
the OpenGL interface. The JOGL / and gluegen /
workspaces must be side-by-side in order for JOGL to build properly. "
At
this stage, we have drafts of packages for both, Gluegen [5] and JOGL [6], but
we got to the stalemate that JOGL continues to need Gluegen’s **code** to build
his own build.xml, so, even if we have Gluegen packaged and installed, what
matters for the correct build of JOGL is the gluegen’s code side by side.
At
first I thought it would be better to generate both packages from a single .spec,
then I decided to create a separate package for Gluegen and provide a tarball
of that Gluegen’s code as Source1 for the compilation of JOGL.
As
Chen Lei said, the fact that JOGL needs this code may mean that it will be blocked
forever for packaging, but I do not particularly see a big problem.
For
more details, please, read the log in bugzilla and give your ideas regarding
this question.
[1] - http://www.scilab.org/
[2] - https: / / jogl.dev.java.net /
[3] - https: / /
gluegen.dev.java.net /
[4] - http://download.java.net/media/jogl/doc/HowToBuild.html
[5] - https: /
/ bugzilla.redhat.com / show_bug.cgi? Id = 439627
[6] - https: /
/ bugzilla.redhat.com / show_bug.cgi? Id = 439630 ------------------------------
Henrique "LonelySpooky" Junior
____________________________________________________________________________________
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com
11:22 a.m.
On Sun, Feb 28, 2010 at 06:39:43AM -0800, Henrique Junior wrote:
Hi, gentlemen,
For some time the inclusion of the software Scilab [1] in our repos has been
barred by various dependencies, which were being resolved with time. Currently,
the biggest reason we do not have this software in our repos is that it relies
in a software called JOGL [2].
The big question here is that JOGL, in his turn, depends on other software
called Gluegen [3] and, more specifically, it depends on the **source tree** of
Gluegen, as explained in the instructions for build [4]:
"Step 5 - Check out the GlueGen source tree:
JOGL GlueGen relies on the project to autogenerate most of the Java and JNI
code for the OpenGL interface. The JOGL / and gluegen / workspaces must be
side-by-side in order for JOGL to build properly. "
You need to figure out why jogl needs gluegen and what the ramification is
for the final package in order to really get this discussion going. The
closer we can make this to a static library issue, the easier time you'll
have justifying an exception. The closer it is to a bundled library, the
less likely an exception is.
-Toshio
3:58 p.m.
You need to figure out why jogl needs gluegen and what the
ramification is
for the final package in order to really get this discussion going. The
closer we can make this to a static library issue, the easier time you'll
have justifying an exception. The closer it is to a bundled library, the
less likely an exception is.
-Toshio
I think that Hans's suggestion (in the devel list) may be a good solution.
--
Henrique "LonelySpooky" Junior
8:49 p.m.
On Sun, Feb 28, 2010 at 06:58:23PM -0300, Henrique Junior wrote:
> You need to figure out why jogl needs gluegen and what the
ramification is
> for the final package in order to really get this discussion going. The
> closer we can make this to a static library issue, the easier time you'll
> have justifying an exception. The closer it is to a bundled library, the
> less likely an exception is.
>
> -Toshio
I think that Hans's suggestion (in the devel list) may be a good solution.
Hans's suggestion may be good. But it depends on what is really going on in
jogl. If jogl could be easily patched to not need gluegen's source code but
we end up doing the gluegen source code then it's a very poor solution.
OTOH, if jogl really needs some private "header" from the gluegen source
then it is a resonable solution (it becomes equivalent to tracking a static
library and is an easier exception to grant than an exception for bundled
libraries.)
So... more informaiton is needed.
-Toshio
5163
days inactive
5164
days old
packaging@lists.fedoraproject.org
3 comments
2 participants
participants (2)
-
Henrique Junior -
Toshio Kuratomi