Re: [gentoo-dev] Re: EAPI spec (was Re: Re: let's clear things up (was Slacker archs))

[Brian Harring]

On Thu, Feb 22, 2007 at 08:11:34PM +0100, Danny van Dyk wrote:
> Am Donnerstag, 22. Februar 2007 17:41 schrieb Brian Harring:
> > Further, getting away from the daft FUD we're trying to 'replace the
> > ebuild format' that was leveled.
> >
> > > Also have a look at our statements regarding overlays again.
> > > Overlays can't be configure properly. Multiple repositories can.
> > > Nobody says there should be no sharing between them, but it needs
> > > to be configured by the user.
> >
> > master_repository is a new one added within the last two weeks;
> > stand corrected.
> Repository defaults have been in a little bit longer I think.
> <looking up>
> 2007-01-26 Ciaran McCreesh <ciaranm@×××××××.org>
> 	* doc/configuration.html.skel,
> 	  paludis/environment/default/default_config.cc,
> 	  paludis/util/collection.hh, paludis/util/collection_concrete.hh: Add
> 	  support for a repository_defaults.conf file.
>
> There we go.

master_repository is required for thirdpartymirrors, which was the 
main stumbling block (and why folks were daftly copying 
$PORTDIR/profiles/thirdpartymirror into the overlay); feature above 
just enables avoiding boilerplate in the repostories/* definitions.


> > SRC_URI restrictions (port, protocol, etc) are one angle of why at
> > least poking them matters- really depends upon what PMS is going to
> > address, standalone spec, or gentoos form- if the latter, then
> > port/protocol restrictions apply, if the former then those
> > restrictions need to wind up somewher as an extension of the spec.
>
> What has that to do with the PMS? PMS doesn't talk about how mirrors
> should work or how to stage files. It's a spec for the package manager.

The point there was that of binding the gentoo specific restrictions 
in somehow; whether y'all jam it into the spec itself (ick), or 
shoving it into a seperate doc.


> What you are talking about are implementation details, and even those
> which are only remotely related to how the package manager handles
> stuff. This matters once we should ever start writing a Gentoo
> Distribution Backstage Spec.

Said spec covers profiles also; mentioning at least the existance of 
the misc STAGE* settings isn't a horrible idea, even if not going into 
detail- anyone digging through the profiles will see them, and likely 
wonder why they're there, and why quite a few profiles specify an 
extra set of use lists.

While writing the sucker out, I'd expect you'll come across things 
where gentoo has a specific way of doing it, which isn't required by 
the manager.  The suggestion would be to track that somehow, or look 
at mangling the devmanual so that it's just diffs against the spec.

Either way, the protocol/port bit was an idle, badly phrase 
suggestion (in other words, take it or leave it).

~harring