1 |
On Sun, 4 Mar 2007 01:51:39 +0900 Jason Stubbs <jstubbs@g.o> |
2 |
wrote: |
3 |
> There were two separate specifications - glep42 and multiple |
4 |
> repositories - that should have been discussed seperately. On a |
5 |
> seperate thread, Marius said something to the effect of "specs are |
6 |
> much easier to extend than to alter". Having read that, I think we |
7 |
> were both wrong - specification of a repository should probably have |
8 |
> been left out completely until repositories had been hashed out. |
9 |
|
10 |
Which is what I was pushing for all along. I was trying to leave |
11 |
multiple repositories entirely out of it -- despite Paludis making use |
12 |
of them -- because the GLEP had nothing to do with multiple |
13 |
repositories. |
14 |
|
15 |
> To sidetrack just a little more, I think this illustrates one of the |
16 |
> reasons why having PMS (aka EAPI-0 spec) completed is so important. |
17 |
> Not only would it allow for Gentoo package manager(s) to be |
18 |
> interchanged/replaced, it would provide a incontrovertible context |
19 |
> for discussion of new features. |
20 |
|
21 |
There aren't going to be any new features in PMS. The only package |
22 |
manager changes that we want to come about as a result of it are bug |
23 |
fixes. |
24 |
|
25 |
Incidentally... Side note on PMS vs EAPI-0: the way PMS is written, |
26 |
it's deliberately very easy to integrate EAPI-1, EAPI-2 or whatever |
27 |
into the document. Consider PMS to be a document that is capable of |
28 |
holding all EAPIs, with EAPI-0 being the only one that's actually there |
29 |
for now. Once EAPI-1 is agreed upon, it can be added to PMS rather than |
30 |
having to be a whole new document. |
31 |
|
32 |
> This is really irrelevant. It's not matter of "if" he gets access but |
33 |
> only as to "when". After the initial work is done and the team is |
34 |
> ready to go public all his "noise" will come out. I can only think of |
35 |
> two choices here: 1) whether you and he both continue to be visceral |
36 |
> or instead try to build a good working relationship; and |
37 |
> 2) whether you discuess any issues with the spec now or when it goes |
38 |
> public. |
39 |
|
40 |
That's a fairly big difference. If it's later on, there won't be lots |
41 |
of holes that we know are there that he can use as some kind of twisted |
42 |
proof that PMS sucks. |
43 |
|
44 |
-- |
45 |
Ciaran McCreesh |
46 |
Mail : ciaranm at ciaranm.org |
47 |
Web : http://ciaranm.org/ |
48 |
Paludis, the secure package manager : http://paludis.pioto.org/ |