public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Manifest issues in the tree
Date: Wed, 16 Jul 2003 11:50:30 -0400	[thread overview]
Message-ID: <3F157446.8000101@gentoo.org> (raw)
In-Reply-To: <3F152250.6020707@codewordt.co.uk>

Dhruba Bandopadhyay wrote:

> Is there really a keyword in FEATURES called 'manifest'?  It is 
> certainly not documented in make.conf.  Where is this declared?

It was in portage for a time, during the 2.0.48_preX series of portage. 
  It basically cross-checks every file related to that package against 
the manifest.  Coupled with the "strict" keyword, it makes portage 
extremely stingy on md5summing files.  A single mismatch like I'm 
getting and it will refuse to go any further.

This is why I am wondering if 'manifest' may be buggy, or we have some 
kind of minor corruption plaguing rsync somehow.

--Kumba


-- 
"Such is oft the course of deeds that move the wheels of the world: 
small hands do them because they must, while the eyes of the great are 
elsewhere."  --Elrond


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-07-16 15:44 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
2003-07-16 15:50   ` Kumba [this message]
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=3F157446.8000101@gentoo.org \
    --to=kumba@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