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
Hi,
On 02/28/2010 03:39 PM, 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. "
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.
AFAIK we have had problems like this before with various bits of Xorg (iirc) needing the sources of other bits to build.
The "usual" solution for this, is to give a package a -source subpackage, which contains the extracted sources (and installs them under /usr/src
So I think the best way to handle this is to package gluegen, and include gluegen's sources as a gluegen-source subpackage, and then make jogl BuildRequire gluegen-source.
Regards,
Hans
Hans de Goede wrote:
AFAIK we have had problems like this before with various bits of Xorg (iirc) needing the sources of other bits to build.
The "usual" solution for this, is to give a package a -source subpackage, which contains the extracted sources (and installs them under /usr/src
So I think the best way to handle this is to package gluegen, and include gluegen's sources as a gluegen-source subpackage, and then make jogl BuildRequire gluegen-source.
Still, this is a very evil workaround. Can JOGL really not be fixed to use an installed gluegen? Why does it need the source?
Kevin Kofler
Still, this is a very evil workaround. Can JOGL really not be fixed to use an installed gluegen? Why does it need the source?
Well, the symbiotic relationship between JOGL and Gluegen is because the Gluegen project is developed by the JOGL project, in principle, to be used only by JOGL.
By Wikipedia: It was originally developed for JOGL, a Java OpenGL library, although the project has since been separated so it can be used with other libraries. It is currently also used in JOAL, which allows Java code to access OpenAL libraries. In the case of JOGL, GlueGen is not only used to bind OpenGL to Java, but also the low-level windowing system APIs on the Windows, X11 and Mac OS X platforms.
Henrique Junior wrote:
Well, the symbiotic relationship between JOGL and Gluegen is because the Gluegen project is developed by the JOGL project, in principle, to be used only by JOGL.
By Wikipedia: It was originally developed for JOGL, a Java OpenGL library, although the project has since been separated so it can be used with other libraries.
That's not a good reason to require a bundled version. It has been separated so it can be used with other libraries, I don't see why JOGL itself can't also use it that way. Technical details very much appreciated!
Kevin Kofler
I think we need some more experienced java packager to accelerate packaging scilab, it can be a new feature for F14. Since scilab may be the best opensource numerical computational software, is there someone interseted in packaging scilab for fedora?
Regard, Chen Lei
在2010-03-01?09:22:33，"Kevin?Kofler"?kevin.kofler@chello.at?写道：
Hans?de?Goede?wrote:
?AFAIK?we?have?had?problems?like?this?before?with?various?bits?of?Xorg ?(iirc)?needing?the?sources?of?other?bits?to?build. ? ?The?"usual"?solution?for?this,?is?to?give?a?package?a?-source?subpackage, ?which?contains?the?extracted?sources?(and?installs?them?under ?/usr/src ? ?So?I?think?the?best?way?to?handle?this?is?to?package?gluegen,?and?include ?gluegen's?sources?as?a?gluegen-source?subpackage,?and?then?make?jogl ?BuildRequire?gluegen-source.
Still,?this?is?a?very?evil?workaround.?Can?JOGL?really?not?be?fixed?to?use? an?installed?gluegen??Why?does?it?need?the?source?
????????Kevin?Kofler
--? devel?mailing?list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
2010/2/28 Chen Lei supercyper@163.com:
I think we need some more experienced java packager to accelerate packaging scilab, it can be a new feature for F14. Since scilab may be the best opensource numerical computational software, is there someone interseted in packaging scilab for fedora?
Regard, Chen Lei
Scilab is, in fact, in advanced packaging stage, waiting for JOGL.
在2010-03-01?11:00:59，"Henrique?Junior"?henriquecsj@gmail.com?写道：
2010/2/28?Chen?Lei?supercyper@163.com:
?I?think?we?need?some?more?experienced?java?packager?to?accelerate?packaging ?scilab,?it?can?be?a?new?feature?for?F14.??Since?scilab?may?be?the?best ?opensource?numerical?computational?software,?is?there?someone?interseted?in ?packaging?scilab?for?fedora?
?Regard, ?Chen?Lei
Scilab?is,?in?fact,?in?advanced?packaging?stage,?waiting?for?JOGL.
A lot of java packages need package from scratch or patch(this may be difficult if you are not provenpackager, since some package maintainers are non-responsive for a long while) for scliab5.2.1.
--? Henrique?"LonelySpooky"?Junior --? devel?mailing?list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Scilab?is,?in?fact,?in?advanced?packaging?stage,?waiting?for?JOGL.
A lot of java packages need package from scratch or patch(this may be difficult if you are not provenpackager, since some package maintainers are non-responsive for a long while) for scliab5.2.1.
Please give us the following list: * package name - maintainer - needed change
Thanks, Alex
Hello, folks. Is there anyone available to review the packages?
gluegen - https://bugzilla.redhat.com/show_bug.cgi?id=572512 jogl - https://bugzilla.redhat.com/show_bug.cgi?id=572515
____________________________________________________________________________________ Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com
On Sun, 2010-02-28 at 15:49 +0100, Hans de Goede wrote:
On 02/28/2010 03:39 PM, Henrique Junior wrote:
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.
AFAIK we have had problems like this before with various bits of Xorg (iirc) needing the sources of other bits to build.
The "usual" solution for this, is to give a package a -source subpackage, which contains the extracted sources (and installs them under /usr/src
So I think the best way to handle this is to package gluegen, and include gluegen's sources as a gluegen-source subpackage, and then make jogl BuildRequire gluegen-source.
Yeah, we did this for Mesa from FC5 through F9. Certainly not ideal, but such is life.
I wouldn't consider this a blocker for packaging, though I'd like to see it fixed eventually. Usually when this kind of source build dependency exists it's not a trivial thing to fix.
- ajax
On Mon, 2010-03-01 at 09:36 -0500, Adam Jackson wrote:
On Sun, 2010-02-28 at 15:49 +0100, Hans de Goede wrote:
On 02/28/2010 03:39 PM, Henrique Junior wrote:
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.
AFAIK we have had problems like this before with various bits of Xorg (iirc) needing the sources of other bits to build.
The "usual" solution for this, is to give a package a -source subpackage, which contains the extracted sources (and installs them under /usr/src
So I think the best way to handle this is to package gluegen, and include gluegen's sources as a gluegen-source subpackage, and then make jogl BuildRequire gluegen-source.
Yeah, we did this for Mesa from FC5 through F9. Certainly not ideal, but such is life.
I wouldn't consider this a blocker for packaging, though I'd like to see it fixed eventually. Usually when this kind of source build dependency exists it's not a trivial thing to fix.
We still do it now for x11vnc with xorg-x11-server.
%package source Summary: Xserver source code required to build VNC server (Xvnc) Group: Development/Libraries BuildArch: noarch
Dave.
-
Adam Jackson -
Aleksandar Kurtakov -
Chen Lei -
David Airlie -
Hans de Goede -
Henrique Junior -
Kevin Kofler