| 1 |
On Mon, Mar 28, 2011 at 11:43 AM, Christoph Mende wrote: |
| 2 |
> On Mon, 2011-03-28 at 16:57 +0200, Thomas Kahle wrote: |
| 3 |
>> On 13:13 Sun 27 Mar , "Paweł Hajdan, Jr." wrote: |
| 4 |
>> > FEATURES=digest results in a scary warning and a possibly dangerous |
| 5 |
>> > re-generation of manifests at the beginning of every emerge: |
| 6 |
>> > |
| 7 |
>> > * The FEATURES=digest setting can prevent corruption from being noticed. |
| 8 |
>> > * The `repoman manifest` command is the preferred way to generate |
| 9 |
>> > * manifests and it is capable of doing an entire repository or category at |
| 10 |
>> > * once. |
| 11 |
>> > |
| 12 |
>> > However, FEATURES=digest is enabled in the developer profile, and only |
| 13 |
>> > in that profile: |
| 14 |
>> > |
| 15 |
>> > $ egrep '^FEATURES=.*digest' -r /usr/portage/profiles/ |
| 16 |
>> > /usr/portage/profiles/targets/developer/make.defaults:FEATURES="collision-protect |
| 17 |
>> > digest multilib-strict sign splitdebug stricter test test-fail-continue |
| 18 |
>> > userpriv usersandbox" |
| 19 |
>> > |
| 20 |
>> > I'd like to suggest removing "digest" from the line above. I've been |
| 21 |
>> > running with the developer profile and -digest in /etc/make.conf, and |
| 22 |
>> > everything is working fine. |
| 23 |
>> |
| 24 |
>> +1. |
| 25 |
>> |
| 26 |
>> I disabled it on the first day and never had any issues. |
| 27 |
> |
| 28 |
> I guess the real question here is: why was it enabled? |
| 29 |
|
| 30 |
because doing active development on ebuilds by definition invalidates |
| 31 |
the manifest. portage didnt use to whine about it at all. a lot |
| 32 |
easier to `emerge foo` without having to manually run `ebuild foo |
| 33 |
manifest` all the damn time. |
| 34 |
|
| 35 |
personally, i use FEATURES=digest on my development machine, but i can |
| 36 |
see how people would find this undesirable as a profile default. |
| 37 |
-mike |
Archives