[gentoo-dev] developer profile, FEATURES=digest

[gentoo-dev] developer profile, FEATURES=digest

["Paweł Hajdan, Jr."]

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

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.

Paweł Hajdan, Jr.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

Re: [gentoo-dev] developer profile, FEATURES=digest

[Thomas Kahle]

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]

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.

Thomas



-- 
Thomas Kahle
http://dev.gentoo.org/~tomka/

[-- Attachment #2: Type: application/pgp-signature, Size: 316 bytes --]

Re: [gentoo-dev] developer profile, FEATURES=digest

[Christoph Mende]

[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]

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.
> 
> Thomas
> 
> 
> 

I guess the real question here is: why was it enabled?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 230 bytes --]

Re: [gentoo-dev] developer profile, FEATURES=digest

[Mike Frysinger]

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

Re: [gentoo-dev] developer profile, FEATURES=digest

[Mike Frysinger]

On Mon, Mar 28, 2011 at 1:03 PM, 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.

oh, and i'm fairly certain that it used to only rebuild Manifests as
necessary (instead of blindly doing it all the time), and it used to
not check the digests of missing files.  the latter though now is
available through FEATURES=assume-digests.
-mike

Re: [gentoo-dev] developer profile, FEATURES=digest

[justin]

[-- Attachment #1: Type: text/plain, Size: 1751 bytes --]

On 28/03/11 19:03, 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.

In my opinion, setting
EBUILD_DEFAULT_OPTS="--skip-manifest"
and using the "undigested" ebuild only with the ebuild command is a
better way, then the FEATURE=digest approach.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: [gentoo-dev] developer profile, FEATURES=digest

[Mike Frysinger]

On Mon, Mar 28, 2011 at 2:18 PM, justin wrote:
> On 28/03/11 19:03, 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.
>
> In my opinion, setting
> EBUILD_DEFAULT_OPTS="--skip-manifest"
> and using the "undigested" ebuild only with the ebuild command is a
> better way, then the FEATURE=digest approach.

highly workflow dependent.  your setup wouldnt cover all of mine.
-mike

Re: [gentoo-dev] developer profile, FEATURES=digest

[Christoph Mende]

[-- Attachment #1: Type: text/plain, Size: 2032 bytes --]

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.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 230 bytes --]

Re: [gentoo-dev] developer profile, FEATURES=digest

[Markos Chandras]

[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]

On Sun, Mar 27, 2011 at 01:13:51PM +0200, "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.
> 
> Paweł Hajdan, Jr.
> 

Yes please do it

Regards,
-- 
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-dev] developer profile, FEATURES=digest

["Paweł Hajdan, Jr."]

[-- Attachment #1: Type: text/plain, Size: 597 bytes --]

On 3/27/11 1:13 PM, "Paweł Hajdan, Jr." wrote:
> 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.

Are there any objections against doing the above?

Christos (angelos), Mike (vapier): your comments don't sound like a
strong "no objections" to me, but they also don't sound like "please
don't do that". I guess you may need to add FEATURES=digest to your
/etc/make.conf after the profile change, but that should generally be
fine, right?

Paweł Hajdan, Jr.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

Re: [gentoo-dev] developer profile, FEATURES=digest

[Mike Frysinger]

On Sat, Apr 2, 2011 at 12:22 PM, "Paweł Hajdan, Jr." wrote:
> On 3/27/11 1:13 PM, "Paweł Hajdan, Jr." wrote:
>> 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.
>
> Are there any objections against doing the above?
>
> Christos (angelos), Mike (vapier): your comments don't sound like a
> strong "no objections" to me, but they also don't sound like "please
> don't do that". I guess you may need to add FEATURES=digest to your
> /etc/make.conf after the profile change, but that should generally be
> fine, right?

drop it
-mike

Re: [gentoo-dev] developer profile, FEATURES=digest

["Paweł Hajdan, Jr."]

[-- Attachment #1: Type: text/plain, Size: 424 bytes --]

On 4/2/11 7:08 PM, Mike Frysinger wrote:
> On Sat, Apr 2, 2011 at 12:22 PM, "Paweł Hajdan, Jr." wrote:
>> On 3/27/11 1:13 PM, "Paweł Hajdan, Jr." wrote:
>>> 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.
>>
>> Are there any objections against doing the above?
>>
> drop it

done.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 194 bytes --]