| 1 |
Thanks for your work mate ! |
| 2 |
|
| 3 |
On 14/01/2013 21:24, Andreas K. Huettel wrote: |
| 4 |
> [CC'ing this to core so noone can complain afterwards.] |
| 5 |
> |
| 6 |
> Since 48h did not lead to any responses positive or negative, I'll start |
| 7 |
> implementing the procedure as given in the original e-mail (quoted below). |
| 8 |
> |
| 9 |
> As also said below, each arch will get a mail before I touch their profile |
| 10 |
> tree and after I've finished. |
| 11 |
> |
| 12 |
> Cheers, Andreas |
| 13 |
> |
| 14 |
> |
| 15 |
> Am Samstag, 12. Januar 2013, 21:47:18 schrieb Andreas K. Huettel: |
| 16 |
>> Hi everyone, |
| 17 |
>> |
| 18 |
>> since Council has approved the creation of a fresh set of EAPI=5 "13.0" |
| 19 |
>> profiles, I would like to volunteer for creating them. The proposed |
| 20 |
>> procedure is outlined below in detail, and I'd be happy for comments. |
| 21 |
>> [If anything below deviates from Council decision, please tell me- not my |
| 22 |
>> intention.] |
| 23 |
>> |
| 24 |
>> One general question comes first, though: Right now, the releases/10.0 |
| 25 |
>> profile directory does the following things: |
| 26 |
>> * mask too-old portage |
| 27 |
>> * set eapi |
| 28 |
>> * add USE=bzip2 |
| 29 |
>> |
| 30 |
>> Is there anything unrelated to EAPI=5 that absolutely must be added to the |
| 31 |
>> new releases/13.0 directory in addition in your opinion? (Whether this is |
| 32 |
>> the right place and was the right place in the beginning for USE=bzip2 is |
| 33 |
>> another question.) |
| 34 |
>> |
| 35 |
>> ### |
| 36 |
>> |
| 37 |
>> The procedure (all paths relative to profiles): |
| 38 |
>> |
| 39 |
>> 1) create directory eapi-5-files, with eapi (containing 5), skeletons for |
| 40 |
>> package.stable.mask etc and a readme |
| 41 |
>> |
| 42 |
>> 2) copy releases/10.0 to releases/13.0, in releases/13.0: |
| 43 |
>> * increase required portage version |
| 44 |
>> * additionally inherit ../../eapi-5-files |
| 45 |
>> * other changes as per question above? |
| 46 |
>> |
| 47 |
>> 3) for each arch in default/linux, |
| 48 |
>> * announce on arch alias (to prevent overlapping commits) |
| 49 |
>> * copy default/linux/${arch}/10.0 to default/linux/${arch}/13.0 and |
| 50 |
>> * change inheritance in the new copy to inherit ../../../../releases/13.0 |
| 51 |
>> instead of ../../../../releases/10.0 |
| 52 |
>> * announce on arch alias (so future changes go into 13.0 tree) |
| 53 |
>> [This describes the simple case. I realize that there are differences in |
| 54 |
>> the directory structure, e.g. powerpc/ppc64/10.0, which is why this step |
| 55 |
>> needs extra care.] |
| 56 |
>> |
| 57 |
>> 4) edit profiles.desc and copy all "10.0 lines" to "13.0 lines", with an |
| 58 |
>> initial setting "dev" (if dev or stable before) or "exp" (if exp before) |
| 59 |
>> This makes repoman check against the new profiles when using developer |
| 60 |
>> profiles. |
| 61 |
>> |
| 62 |
>> 5) announce the state on the dev list, urging devs to update their symlink |
| 63 |
>> manually and !test! |
| 64 |
>> |
| 65 |
>> 6) wait one / two weeks |
| 66 |
>> |
| 67 |
>> 7) in profiles.desc, mark all 13.0 profiles stable that were stable in |
| 68 |
>> 10.0, and remove the lines for the 10.0 profiles. This makes eselect |
| 69 |
>> profile now only offer the new ones, and repoman test by default against |
| 70 |
>> 13.0 profiles. |
| 71 |
>> |
| 72 |
>> 8) mark all 10.0 profiles as deprecated by creating a "deprecated" file |
| 73 |
>> (containing the replacement suggestion) in the directory. This makes |
| 74 |
>> portage warn users to upgrade (suggesting a new profile for them), and |
| 75 |
>> repoman ignore the 10.0 profiles. |
| 76 |
>> |
| 77 |
>> 9) long waiting time as decided by Council |
| 78 |
>> |
| 79 |
>> ### |
| 80 |
>> |
| 81 |
>> Everything that does NOT use/inherit 10.0 will remain unaffected, and |
| 82 |
>> whoever responsible may have to take care of that some time before (in |
| 83 |
>> step 10) the main profile directory becomes EAPI=5. This means e.g. |
| 84 |
>> hardened, ulibc, prefix or bsd. |
| 85 |
>> |
| 86 |
>> Cheers, |
| 87 |
>> Andreas |
| 88 |
> |
| 89 |
> |
Archives