On Mon, 2011-03-28 at 13:03 -0400, Mike Frysinger wrote: > On Mon, Mar 28, 2011 at 11:43 AM, Christoph Mende wrote: > > On Mon, 2011-03-28 at 16:57 +0200, Thomas Kahle wrote: > >> On 13:13 Sun 27 Mar , "Paweł Hajdan, Jr." wrote: > >> > FEATURES=digest results in a scary warning and a possibly dangerous > >> > re-generation of manifests at the beginning of every emerge: > >> > > >> > * The FEATURES=digest setting can prevent corruption from being noticed. > >> > * The `repoman manifest` command is the preferred way to generate > >> > * manifests and it is capable of doing an entire repository or category > >> > at > >> > * once. > >> > > >> > However, FEATURES=digest is enabled in the developer profile, and only > >> > in that profile: > >> > > >> > $ egrep '^FEATURES=.*digest' -r /usr/portage/profiles/ > >> > /usr/portage/profiles/targets/developer/make.defaults:FEATURES="collision-protect > >> > digest multilib-strict sign splitdebug stricter test test-fail-continue > >> > userpriv usersandbox" > >> > > >> > I'd like to suggest removing "digest" from the line above. I've been > >> > running with the developer profile and -digest in /etc/make.conf, and > >> > everything is working fine. > >> > >> +1. > >> > >> I disabled it on the first day and never had any issues. > > > > I guess the real question here is: why was it enabled? > > because doing active development on ebuilds by definition invalidates > the manifest. portage didnt use to whine about it at all. a lot > easier to `emerge foo` without having to manually run `ebuild foo > manifest` all the damn time. > > personally, i use FEATURES=digest on my development machine, but i can > see how people would find this undesirable as a profile default. > -mike >
Ah, yes, now that you mention it, I really like it that I can just "repoman full" instead of "repoman manifest; repoman full". Although for testing I use ebuild foo.ebuild digest clean install most of the time, so it's not relevant there.
signature.asc
Description: This is a digitally signed message part