1 |
Hi Grobian, |
2 |
|
3 |
on AIX, obviously I do want to use the IBM JDK, especially as they |
4 |
provide a 'redist' tar ball, which I do have the ebuild for already. |
5 |
|
6 |
Besides generic prefix support, there are only a few very minor changes |
7 |
necessary to the existent upstream ibm-jdk-bin ebuilds (yes, IBM |
8 |
provides their JDK for {x86,amd64}-linux and {ppc,ppc64}-linux too) to |
9 |
use IBM's "j632redist.tar.gz" (or "j664redist.tar.gz" for 64bit), as its |
10 |
content is quite identical to what is found in the linux tar balls. |
11 |
|
12 |
Unfortunately, IBM does not put version numbers in the redist filename |
13 |
(besides 5 and 6 for the main java version). When they update their |
14 |
site, the old version cannot be retrieved any more. |
15 |
What whould you suggest to do here? |
16 |
At the moment, I advise the user to rename "j632redist.tar.gz" to |
17 |
something like "j632redist-${PV}.tar.gz" when downloading. |
18 |
|
19 |
But the main problem as long as we are semi-auto-syncing from main tree |
20 |
is: When I add dev-java/ibm-jdk-bin to the Prefix tree, semi-auto-sync |
21 |
will fail on that, because additional SRC_URI files need to be |
22 |
downloaded *manually* to create the Manifest, requiring a login at IBM. |
23 |
|
24 |
What seems possible for me now is (first is preferred): |
25 |
*) Put it in prefix tree, but ignore it in auto-sync. |
26 |
*) Keep it in my private overlay until we are in main tree. |
27 |
*) Create a new package in prefix only, being a quite identical copy |
28 |
from ibm-jdk-bin. |
29 |
|
30 |
Thoughts? Do you have a mechanism to exclude a package from auto-sync, |
31 |
even when it exists upstream? |
32 |
|
33 |
Thanks! |
34 |
|
35 |
/haubi/ |
36 |
-- |
37 |
Michael Haubenwallner |
38 |
Gentoo on a different level |