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: Mon, 29 Aug 2005 05:01:55 -0500 [thread overview]
Message-ID: <20050829100154.GG18464@nightcrawler> (raw)
In-Reply-To: <20050902095737.1c642de5@andy.genone.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]
On Fri, Sep 02, 2005 at 09:57:37AM +0200, Marius Mauch wrote:
> On 08/29/05 Brian Harring wrote:
>
> > On Fri, Sep 02, 2005 at 08:17:39AM +0200, Marius Mauch wrote:
> > > Don't mind moving them, BUT
> > > - metadata is a stupid location for them for several reasons
> > being?
> > metadata already holds global repository information, time of
> > repositories generation, pregenerated cache, glsa set...
> > It holds global metadata for the repository.
>
> a) doesn't exist in CVS
Not an arguement against it, since any other directory must also be
added.
> b) is generally associated with "populated by cvs->rsync"
Only by those who deal in cvs; minority I might add.
> c) becomes just another dumping ground (it should only hold the cache
> IMO)
Whatever directory gets added, suffers the same potential. Regarding
the cache, see below.
> d) This isn't "metadata" at all
The repository is a container of data; the files targeted are data
about the repository data.
That's the exact definition of metadata, data about data.
What's the pregenerated cache, or moreso, what's the cache? data
lifted from ebuilds (build data). The naming is apt.
Storing the repository metadata in a common directory also makes sense
if you consider the fact that people sharing their own repository
*may* be distributing a pregenerated cache alongside; it's data that's
bound to the specific layout of our current form of ebuild repository.
So... I'm not seeing how this is anything but the right location for
it. global is a fitting name if it's a global template for ebuilds,
something that is directly used in all ebuilds. These files aren't,
they're strictly a higher layer of data/descriptions for the data
ebuilds group hold/export (p.mask breaks down on this, but it's the
sole exception nearest I can figure).
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-29 10:05 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
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 [this message]
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=20050829100154.GG18464@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