From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] proposed shift of files in the tree of non profiles files into seperate dir
Date: Sat, 27 Aug 2005 06:34:15 -0500 [thread overview]
Message-ID: <20050827113415.GZ1701@nightcrawler> (raw)
In-Reply-To: <0GLGT3211E5W3.18901035628RD8F@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]
On Sat, Aug 27, 2005 at 01:17:50PM +0200, Kevin F. Quinn wrote:
> On 27/8/2005 10:42:25, Brian Harring (ferringb@gentoo.org) wrote:
> > Hola all.
> >
> > Straight to the point, I'm proposing that the following files-
> > arch.list
> > categories
> > use.desc
> > use.local.desc
> > package.mask
> > updates
> >
> > be moved out of the profiles directory in the tree
>
> Not sure about package.mask. I thought that was part of the profile,
> as different profiles might package.mask separately. I know I use it
> in /etc/profile to postpone updates.
Rough filtering stack-
profiles/package.mask
/etc/make.profile/package.mask (incremental through subprofiles)
users package.mask, and users package.unmask
Ordered it in that fashion to show that it's effectively repository
filtering, profile filtering, user filtering; if you view it as
seperate entities with filters stacked up (how the rewrite implements
it), package.mask being repository metadata becomes clear.
Basically, think of it this way; what files/data *must* stay with a
repository? If I'm using (say) gentopia ebuilds, the p.mask they use
is specific to _their_ repository; my official gentoo repository
should not be p.mask'ing there stuff, it should only affect itself,
and any repository that is slaved to it (overlays, which aren't stand
alone).
At least that's what I think :)
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-27 11:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 8:42 [gentoo-dev] proposed shift of files in the tree of non profiles files into seperate dir Brian Harring
2005-08-27 11:17 ` Kevin F. Quinn
2005-08-27 11:32 ` Fernando J. Pereda
2005-08-27 11:38 ` Brian Harring
2005-08-27 11:45 ` Fernando J. Pereda
2005-08-27 11:34 ` Brian Harring [this message]
2005-08-27 13:29 ` Kevin F. Quinn
2005-08-27 13:33 ` Brian Harring
2005-08-29 17:27 ` Chris Gianelloni
2005-08-29 20:36 ` Brian Harring
2005-08-29 21:48 ` Chris Gianelloni
2005-08-29 22:24 ` Brian Harring
2005-08-30 12:29 ` Chris Gianelloni
2005-08-30 6:03 ` Brian Harring
2005-08-30 13:08 ` Chris Gianelloni
2005-08-30 13:28 ` Marius Mauch
2005-08-30 13:31 ` Francesco R
2005-09-02 6:17 ` Marius Mauch
2005-08-29 8:23 ` Brian Harring
2005-09-02 7:57 ` Marius Mauch
2005-08-29 10:01 ` Brian Harring
2005-08-30 11:00 ` Marius Mauch
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=20050827113415.GZ1701@nightcrawler \
--to=ferringb@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