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