| 1 |
On 02/10/2013 03:34 PM, Michał Górny wrote: |
| 2 |
> On Sun, 10 Feb 2013 17:06:39 -0500 |
| 3 |
> James Cloos <cloos@×××××××.com> wrote: |
| 4 |
> |
| 5 |
>>>>>>> "AKH" == Andreas K Huettel <dilfridge@g.o> writes: |
| 6 |
>> |
| 7 |
>> AKH> To be honest I did not really see the necessity since the "big red |
| 8 |
>> AKH> warning" exactly tells you what to do (and even which profile to |
| 9 |
>> AKH> pick, which would be more complicated in a news item). |
| 10 |
>> |
| 11 |
>> But it doesn't tell one why the change was made, what differences to |
| 12 |
>> expect once it is done. |
| 13 |
>> |
| 14 |
>> What does: |
| 15 |
>> |
| 16 |
>> diff -uNr profiles/default/linux/amd64/10.0/eapi profiles/default/linux/amd64/13.0/eapi |
| 17 |
>> --- profiles/default/linux/amd64/10.0/eapi 2009-08-17 14:54:00.000000000 -0400 |
| 18 |
>> +++ profiles/default/linux/amd64/13.0/eapi 2013-01-20 06:31:02.000000000 -0500 |
| 19 |
>> @@ -1 +1 @@ |
| 20 |
>> -2 |
| 21 |
>> +5 |
| 22 |
>> |
| 23 |
>> actually *do* to one's system? |
| 24 |
> |
| 25 |
> Out of curiosity, does portage suggest switching to the new profiles |
| 26 |
> even if it doesn't support its EAPI? |
| 27 |
|
| 28 |
Yes, although it's possible to include additional instructions in the |
| 29 |
deprecated file, as you can see in the code here: |
| 30 |
|
| 31 |
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=blob_plain;f=pym/portage/package/ebuild/deprecated_profile_check.py;h=2acf8e3c2e189eb76cfda2ad4743ce238fc81230;hb=HEAD |
| 32 |
|
| 33 |
It interprets all lines after the first one as upgrade instructions. |
| 34 |
-- |
| 35 |
Thanks, |
| 36 |
Zac |
Archives