public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] developer profile, FEATURES=digest
Date: Sun, 27 Mar 2011 13:13:51 +0200	[thread overview]
Message-ID: <4D8F1BEF.8040203@gentoo.org> (raw)

[-- 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 --]

             reply	other threads:[~2011-03-27 11:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27 11:13 "Paweł Hajdan, Jr." [this message]
2011-03-28 14:57 ` [gentoo-dev] developer profile, FEATURES=digest Thomas Kahle
2011-03-28 15:43   ` Christoph Mende
2011-03-28 17:03     ` Mike Frysinger
2011-03-28 17:09       ` Mike Frysinger
2011-03-28 18:18       ` justin
2011-03-28 18:40         ` Mike Frysinger
2011-03-28 19:01       ` Christoph Mende
2011-03-28 17:32 ` Markos Chandras
2011-04-02 16:22 ` "Paweł Hajdan, Jr."
2011-04-02 17:08   ` Mike Frysinger
2011-04-02 20:39     ` "Paweł Hajdan, Jr."

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D8F1BEF.8040203@gentoo.org \
    --to=phajdan.jr@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox