public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Manifest issues in the tree
Date: Thu, 17 Jul 2003 18:59:14 -0400	[thread overview]
Message-ID: <200307171859.19235.vapier@gentoo.org> (raw)
In-Reply-To: <3F166EF1.6050604@codewordt.co.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 17 July 2003 05:40, Dhruba Bandopadhyay wrote:
> 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'.

the manifest FEATURE is a fleeting one ...
that is to say it isnt documented because it isnt going to exist for long ...
forget about it, go home, kiss your loved ones, and get a good nites sleep.
- -mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iQIVAwUBPxcqRkFjO5/oN/WBAQLxqA//TXy7pqIwpKb9I7oTt8ZZK6h5if0QfluU
qWq0E1Wmro+fRbsNP/S/BjBFIBGVivwBW3JaG8N9dRDh9fsUQno6TfFKoQQM9J8T
pLoKmp/A4ggEm0Rdk9PpmCio24QJ6zhga1i1tuJsnvUy00W1OmcMZLdGko5yf5nc
ICYa9yCVjiv6Z92unGiSlLhMl8XAuAjBIg/zWn1d9dO4Gj2I7xf3LBe2zwgrT44B
h30RYSYL7Qaza1Xk+7kNsbnD6gdqvnIxQ+vxeylETAB0BpplCrKHCbbQNhIm8Z6n
7nsmOX1rfKX6olG5Z83hbF2STCfuIr5fTacXIH2SDuZD2OgRuNB0deXXpdulQ/FG
US/mnnJcZ3xgPal5NbIFylXFqNpkRTq11kBWX8r4bsaUs7Lm3I+qm1z7AtaKu1nl
g6t28t9kB9ypW8BR+zJZwDH85h2i+GNn40a1AeWxhE3hzePSIr2NXM/ap20DX5cA
8TWnWWt87abqwQ8mL+2BS1cpgArIJjOOkkLNYf+0usIcAiFyywmqprspCbRNXs1E
UhvOV4h55IKwzyth4Q5skpouuze5pr843JinntQfEK/PH8hWmSNSVwQJ1NBYaCba
EMnccGMX0sdYz9txAmrQAAZoNxDXWllDMsn62m8AudA02w4aSJK14xeX9M84Uyvl
tZW11nLoBMA=
=Htqh
-----END PGP SIGNATURE-----

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-07-17 22:59 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
2003-07-17  8:58       ` Kumba
2003-07-17  9:55         ` Dhruba Bandopadhyay
2003-07-17 22:59       ` Mike Frysinger [this message]
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=200307171859.19235.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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