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