1 |
Am Donnerstag, 22. Februar 2007 17:41 schrieb Brian Harring: |
2 |
> On Thu, Feb 22, 2007 at 05:07:22PM +0100, Danny van Dyk wrote: |
3 |
> > Am Donnerstag, 22. Februar 2007 14:26 schrieb Brian Harring: |
4 |
> > > On Thu, Feb 22, 2007 at 04:13:11AM +0000, Ciaran McCreesh wrote: |
5 |
> > > > On Thu, 22 Feb 2007 04:04:37 +0000 Steve Long |
6 |
> > > > |
7 |
> > > > <slong@××××××××××××××××××.uk> wrote: |
8 |
> > > > | In process terms, I can't understand why the team working on |
9 |
> > > > | it isn't a pkgcore dev (eg marienz if you can't communicate |
10 |
> > > > | with ferringb) |
11 |
> > > > |
12 |
> > > > b) they're more interested in replacing |
13 |
> > > > the ebuild format |
14 |
> > > |
15 |
> > > Pure and absolute FUD; recall which project has added |
16 |
> > > incompatible version extensions, which is dropping running *rm |
17 |
> > > when reinstalling the same ver, which *still* doesn't actually |
18 |
> > > implement overlay logic, leading to overlay authors having to |
19 |
> > > copy master files into each overlay branch. |
20 |
> > |
21 |
> > Please have a look at our code before you make such claims. |
22 |
|
23 |
I meant the overlay logic, and my share of this discussion is still |
24 |
down the mail. Yet you discussed things I didn't even remotely mention. |
25 |
|
26 |
> Further, getting away from the daft FUD we're trying to 'replace the |
27 |
> ebuild format' that was leveled. |
28 |
> |
29 |
> > Also have a look at our statements regarding overlays again. |
30 |
> > Overlays can't be configure properly. Multiple repositories can. |
31 |
> > Nobody says there should be no sharing between them, but it needs |
32 |
> > to be configured by the user. |
33 |
> |
34 |
> master_repository is a new one added within the last two weeks; |
35 |
> stand corrected. |
36 |
Repository defaults have been in a little bit longer I think. |
37 |
<looking up> |
38 |
2007-01-26 Ciaran McCreesh <ciaranm@×××××××.org> |
39 |
* doc/configuration.html.skel, |
40 |
paludis/environment/default/default_config.cc, |
41 |
paludis/util/collection.hh, paludis/util/collection_concrete.hh: Add |
42 |
support for a repository_defaults.conf file. |
43 |
|
44 |
There we go. |
45 |
|
46 |
> > > > And what on earth do infrastructure have to do with a package |
47 |
> > > > manager specification? |
48 |
> > > |
49 |
> > > Wolf31o2 (chris) is releng moreso; one of the few folks doing |
50 |
> > > non-trivial things with the profiles pretty much, with long term |
51 |
> > > experience doing so. |
52 |
> > > |
53 |
> > > In that regard, he's one of a few handful of people who basically |
54 |
> > > could be considered profile experts- further, he's a catalyst |
55 |
> > > monkey, which at least currently, is the stage building method. |
56 |
> > |
57 |
> > He said there would be no need for infrastructure to be involved; a |
58 |
> > claim i back. Nobody said Chris shouldn't be involved |
59 |
> |
60 |
> <snip> |
61 |
> |
62 |
> > Read again, he did not dismiss Chris, he dismissed the claim that |
63 |
> > Infrastructure should send somebody to discuss the package manager |
64 |
> > standard. |
65 |
|
66 |
> SRC_URI restrictions (port, protocol, etc) are one angle of why at |
67 |
> least poking them matters- really depends upon what PMS is going to |
68 |
> address, standalone spec, or gentoos form- if the latter, then |
69 |
> port/protocol restrictions apply, if the former then those |
70 |
> restrictions need to wind up somewher as an extension of the spec. |
71 |
What has that to do with the PMS? PMS doesn't talk about how mirrors |
72 |
should work or how to stage files. It's a spec for the package manager. |
73 |
|
74 |
What you are talking about are implementation details, and even those |
75 |
which are only remotely related to how the package manager handles |
76 |
stuff. This matters once we should ever start writing a Gentoo |
77 |
Distribution Backstage Spec. |
78 |
|
79 |
> Re: dismissing chris being seperate from dismissing infra, yep, |
80 |
> misinterpretted the phrasing- still would suggest hauling in one of |
81 |
> the actual profile/catalyst monkeys however since some of the stuff |
82 |
> they have in there aren't well documented. |
83 |
s/well//. And I don't think that anything or anyone speaks or spoke |
84 |
against Chris getting access to PMS and commenting on it. And to |
85 |
reiterate: this holds true for all council members. |
86 |
|
87 |
Danny |
88 |
-- |
89 |
Danny van Dyk <kugelfang@g.o> |
90 |
Gentoo/AMD64 Project, Gentoo Scientific Project |
91 |
-- |
92 |
gentoo-dev@g.o mailing list |