From: Dhruba Bandopadhyay <dhruba@codewordt.co.uk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Manifest issues in the tree
Date: Thu, 17 Jul 2003 10:40:01 +0100 [thread overview]
Message-ID: <3F166EF1.6050604@codewordt.co.uk> (raw)
In-Reply-To: <20030716115042.GA8123@sdf.lonestar.org>
Tavis Ormandy wrote:
> On Wed, Jul 16, 2003 at 11:00:48AM +0100, Dhruba Bandopadhyay wrote:
>
>>Is there really a keyword in FEATURES called 'manifest'? It is
>>certainly not documented in make.conf. Where is this declared?
>
>
> # 'strict' causes portage to react strongly to conditions that
> # have the potential to be dangerous -- like missing
> # or incorrect Manifest files.
>
That is 'strict'. I was asking about 'manifest'.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-17 8:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 8:25 [gentoo-dev] Manifest issues in the tree Kumba
2003-07-16 10:00 ` Dhruba Bandopadhyay
2003-07-16 11:50 ` Tavis Ormandy
2003-07-17 9:40 ` Dhruba Bandopadhyay [this message]
2003-07-17 8:58 ` Kumba
2003-07-17 9:55 ` Dhruba Bandopadhyay
2003-07-17 22:59 ` Mike Frysinger
2003-07-16 15:50 ` Kumba
2003-07-17 0:25 ` Mike Frysinger
2003-07-17 2:05 ` Brad Cowan
2003-07-17 6:06 ` Kumba
2003-07-17 21:58 ` Mike Frysinger
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=3F166EF1.6050604@codewordt.co.uk \
--to=dhruba@codewordt.co.uk \
--cc=gentoo-dev@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