Bugzilla Bug 55139

The ebuild (marked ~x86) for glpk cannot merge since it requires itself to be
already merged (er, quite unlikely if I'm installing it).
The problem is in the Java section. During compile, the Java sections require
the presence of a installed glpk library; specifically, see
contrib/jni/c/Makefile for a line ending in -lglpk.
This can in principle not be avoided: compiling the java components requires to
have an installation already.
The original author did not notice this, possibly because he first implemented
a simple ebuild, and later added the Java part, which did install because a
glpk library was then in place.

I propose therefore to take out the Java section; it is not meant to be
compiled with the rest of the package but later, as an add-on.

Reproducible: Always
Steps to Reproduce:
1. Start from a machine with no glpk installed
2. ACCEPT_KEYWORDS=~x86 emerge app-sci/glpk

Actual Results:  
Crash occurs in the Java section, since it does not find the glpk library (it
has been compiled, but is not yet merged!)

Expected Results:  
Installation of glpk libraries was expected.

Compiler:
gcc (GCC) 3.3.3 20040412 (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, pie-8.7.6)

Created an attachment (id=34123) [details]
Ebuild without Java support

This ebuild installs glpk also if no glpk is already installed in the system.
Java add-on support has been taken out.

if you don't need java support, you can get around it by remove java support
like so:

# USE="doc -java" ACCEPT_KEYWORDS="~x86" emerge -av app-sci/glpk

Hi Stephan,
what I'm worried is that users should not be forced to browse through 
the bugzilla when they install glpk. If it is installed as a dependency 
of e.g. Kst, it becomes just frustrating.

I think that it should be a priority that the ebuild be able to work
by itself without user intervention.

That said, if someone manages to implement Java-component compilation
without a glpk already merged, I'll be happy - but until then, between
missing Java component and crashing ebuild, I'd take the missing Java.

Maybe the maintainer would be happy to know about this bug. Re-assigning.

I'm going to take the route of just removing the 4.2 version, as I'm pushing
4.7 to stable x86 now.

This would have been the solved long since if I knew about the bug.