1 |
On 07-05-2009 18:23:17 +0200, Michael Haubenwallner wrote: |
2 |
> Unfortunately, IBM does not put version numbers in the redist filename |
3 |
> (besides 5 and 6 for the main java version). When they update their |
4 |
> site, the old version cannot be retrieved any more. |
5 |
> What whould you suggest to do here? |
6 |
> At the moment, I advise the user to rename "j632redist.tar.gz" to |
7 |
> something like "j632redist-${PV}.tar.gz" when downloading. |
8 |
|
9 |
That sounds like a problem in itself. Are you allowed to mirror the |
10 |
file? If not, you need fetchrestriction anyway (old Java ebuilds did |
11 |
this), and you can easily instruct the user how to save the file. |
12 |
|
13 |
> But the main problem as long as we are semi-auto-syncing from main tree |
14 |
> is: When I add dev-java/ibm-jdk-bin to the Prefix tree, semi-auto-sync |
15 |
> will fail on that, because additional SRC_URI files need to be |
16 |
> downloaded *manually* to create the Manifest, requiring a login at IBM. |
17 |
|
18 |
Well, depends :) |
19 |
|
20 |
> What seems possible for me now is (first is preferred): |
21 |
> *) Put it in prefix tree, but ignore it in auto-sync. |
22 |
|
23 |
if in Prefix tree, but not in gentoo-x86, we never sync, of course |
24 |
|
25 |
> *) Keep it in my private overlay until we are in main tree. |
26 |
|
27 |
better put it in the main tree/Prefix tree then |
28 |
|
29 |
> *) Create a new package in prefix only, being a quite identical copy |
30 |
> from ibm-jdk-bin. |
31 |
|
32 |
Probably hack up the ebuild, like I did for solaris in the sun-jdk-bin |
33 |
ebuild. |
34 |
|
35 |
> Thoughts? Do you have a mechanism to exclude a package from auto-sync, |
36 |
> even when it exists upstream? |
37 |
|
38 |
Yeah, I can exclude packages, such as portage, since syncing them just |
39 |
makes a mess :) |
40 |
|
41 |
|
42 |
-- |
43 |
Fabian Groffen |
44 |
Gentoo on a different level |