| 1 |
On 07/15/2013 05:52 PM, René Berber wrote: |
| 2 |
> On 7/15/2013 2:14 PM, Zac Medico wrote: |
| 3 |
>> On 07/15/2013 06:36 AM, Burcin Erocal wrote: |
| 4 |
>>> Hi, |
| 5 |
>>> |
| 6 |
>>> I am still getting the "Your current profile is deprecated ..." |
| 7 |
>>> messages. I guess this can be resolved with the attached patch. |
| 8 |
>>> |
| 9 |
>>> Is there any reason not to bump the pointers in prefix profiles to 13.0 |
| 10 |
>>> versions instead of the deprecated 10.0 ones that used right now? |
| 11 |
>> |
| 12 |
>> Alternatives are discussed here: |
| 13 |
>> |
| 14 |
>> http://thread.gmane.org/gmane.linux.gentoo.alt/6552 |
| 15 |
>> |
| 16 |
>> Since the bootstrap-prefix script [1] now uses |
| 17 |
>> prefix-portage-2.2.01.21864 which supports EAPI 5, updating the existing |
| 18 |
>> profiles in-place is feasible, though it may cause some some upgrade |
| 19 |
>> hassle for anyone who still has an older version of prefix-portage which |
| 20 |
>> does not support EAPI 5. |
| 21 |
>> |
| 22 |
>> [1] |
| 23 |
>> http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay/scripts/bootstrap-prefix.sh?format=txt |
| 24 |
>> |
| 25 |
> |
| 26 |
> What about the command shown with the message (eselect profile set |
| 27 |
> default/linux/amd64/13.0/no-multilib), would that work? |
| 28 |
|
| 29 |
No, that deprecation message is inherited from a non-prefix profile, so |
| 30 |
it is inappropriate. The only appropriate solutions are discussed here: |
| 31 |
|
| 32 |
http://thread.gmane.org/gmane.linux.gentoo.alt/6552 |
| 33 |
|
| 34 |
It's possible for the prefix profile to override the deprecation |
| 35 |
message, which might be a good idea, in order to prevent people from |
| 36 |
switching to a non-prefix profile accidentally. |
| 37 |
-- |
| 38 |
Thanks, |
| 39 |
Zac |
Archives