1 |
On Mon, 2006-06-12 at 19:04 -0400, Luis Francisco Araujo wrote: |
2 |
> Stephen Bennett wrote: |
3 |
> > Continuing in the series of issues raised during the previous package |
4 |
> > manager discussions, I'd like to continue by mentioning the tree |
5 |
> > format. At present, it isn't defined beyond "what the current portage |
6 |
> > supports", which is frankly a fairly silly way to do things. Following |
7 |
> > discussion in #gentoo-portage, I'd like to set out to change that. |
8 |
> > |
9 |
> > My current idea is to draw up a formal specification of what ebuilds |
10 |
> > are allowed to do, and what to assume about the environment in which |
11 |
> > they run, as well as defining the formats of everything under |
12 |
> > profiles/, metadata.xml files, and other auxiliary information in the |
13 |
> > tree. I would envision the first version of this document to more or |
14 |
> > less codify existing practise, perhaps excluding some dubious tricks |
15 |
> > that are known to break in some cases. Generally, it should be possible |
16 |
> > to make the tree conform to the first version of the specification by |
17 |
> > changes no more significant than currently have QA bugs filed for them. |
18 |
> > |
19 |
> > It seems fairly obvious that any effort of this kind could potentially |
20 |
> > have implications, albeit hopefully very minor, across more or less all |
21 |
> > aspects of the tree, and so I'd like to seek as wide a range of input |
22 |
> > as possible before going ahead with it. The QA and Portage teams, based |
23 |
> > on my enquiries in IRC, seem broadly in favour, and I would imagine |
24 |
> > that this could be very helpful to Gentoo/ALT as well, so I'd like |
25 |
> > opinions from others at this point. Would you support such an effort, |
26 |
> > whether passively or actively? Would you oppose it? If so, why? Final |
27 |
> > implementation of it would I assume require the Council's approval; |
28 |
> > while I won't ask at this stage for a formal discussion I'd appreciate |
29 |
> > the views of its members on whether such an initiative is likely to |
30 |
> > pass. |
31 |
> > |
32 |
> > Any input is gratefully received. |
33 |
> > |
34 |
> I like the idea. This would be some kind of portage-tree standard? |
35 |
|
36 |
It's been one of the missing cornerstones of the whole equation. Lets |
37 |
get it done and get it done right. |
38 |
|
39 |
One thing I do ask...Lets all start now getting used to calling the |
40 |
"portage tree" something different. I'm all for terms like "the tree" or |
41 |
"the ebuild tree" or "the package tree" but at this point, given the |
42 |
prompting subject matter, the idea of it being a tree which belongs to |
43 |
portage seems outdated. This may seem like a small thing (like the teams |
44 |
vs. herds argument that has been brought up countless times before) but |
45 |
it is the silly little things like this that really do lower the mental |
46 |
bar for new and exciting things to happen. |
47 |
|
48 |
Thanks, |
49 |
|
50 |
--Dan |