1 |
Hi François, |
2 |
|
3 |
On 06/08/2012 02:13 AM, François Bissey wrote: |
4 |
> There are a lot of ebuilds masked by EAPI=4, as the bootstrap portage only |
5 |
> support EAPI=<3. |
6 |
|
7 |
> With 2.3.0 all versions of perl are masked either by missing keywords or |
8 |
> EAPI=4. |
9 |
|
10 |
> Does bootstrapping on aix require special instructions that I have missed? |
11 |
|
12 |
Unfortunately, for way too long time now I didn't find time to keep prefix-launcher |
13 |
up-to-date enough to keep being able to bootstrap current Prefix. The most important |
14 |
thing to do would be upgrading portage itself, which requires upgrading to python-2.7. |
15 |
|
16 |
However, in theory, prefix-launcher doesn't do much more than what is shown in the |
17 |
bootstrap guides, except to bundle these commands into one super-package. In fact, |
18 |
prefix-launcher isn't much more than what is $EPREFIX/tmp in the bootstrap guides. |
19 |
|
20 |
But I'm not aware of anyone having tried to bootstrap along the bootstrap guide for |
21 |
Solaris on AIX (or Interix) yet - actually I'm surprised to see some conditions for |
22 |
these platforms in bootstrap-prefix.sh. |
23 |
|
24 |
One of the major features of prefix-launcher over the current guide is to be able |
25 |
to carry and apply patches for various packages, which often is necessary for the |
26 |
more exotic platforms like AIX, Interix, HP-UX. This most likely is because these |
27 |
platforms are rarely available to the upstream package maintainers to test on. |
28 |
|
29 |
So you're welcome to either provide patches for prefix-launcher (trunk) to upgrade to |
30 |
python-2.7 and current prefix-portage, or try fixing the Solaris bootstrap guide for AIX. |
31 |
|
32 |
/haubi/ |
33 |
|
34 |
PS: I do have buildbot slaves doing weekly Prefix bootstraps (32bit only) using prefix- |
35 |
launcher-trunk on a bunch of different platforms - including AIX 5.3, 6.1, 7.1, as |
36 |
well as various HP-UX, Solaris, Linux, Interix boxes - failing for too long time now. |