| 1 |
On 02/18/2013 10:13 AM, Fabian Groffen wrote: |
| 2 |
> On 17-02-2013 11:38:41 -0800, Zac Medico wrote: |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
>> The prefix/linux/${ARCH} profiles currently inherit from the deprecated |
| 6 |
>> 10.0 profiles. There are at least a couple of options for migration: |
| 7 |
>> |
| 8 |
>> (1) update existing profiles in-place (not nice for people running |
| 9 |
>> pre-EAPI-5 portage) |
| 10 |
> |
| 11 |
> This should hardly be anyone in Prefix (I think) |
| 12 |
|
| 13 |
You would know better about it than I. |
| 14 |
|
| 15 |
>> (2) deprecate prefix/linux/${ARCH} profiles, and add |
| 16 |
>> prefix/linux/13.0/${ARCH} profiles to replace them (this is |
| 17 |
>> analogous to the approach used for non-prefix profiles) |
| 18 |
>> |
| 19 |
>> I would suggest to go with (2), in order to make things smooth for |
| 20 |
>> pre-EAPI-5 portage users. |
| 21 |
> |
| 22 |
> Yes, but given that we've always been on bleeding edge, I'd be fine with |
| 23 |
> (1) as well. But if someone wants to implement (2), I'm not going to |
| 24 |
> block that in any way. |
| 25 |
|
| 26 |
Well, if you decide to go with (2), you should probably first update |
| 27 |
bootstrap-prefix.sh [1] to use a newer portage version, since it |
| 28 |
currently uses prefix-portage-2.2.01.20837.tar.bz2 which doesn't support |
| 29 |
EAPI 5. |
| 30 |
|
| 31 |
[1] |
| 32 |
http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay/scripts/bootstrap-prefix.sh?format=txt |
| 33 |
-- |
| 34 |
Thanks, |
| 35 |
Zac |
Archives