1 |
On Sunday 27 November 2005 18:43, Diego 'Flameeyes' Pettenò wrote: |
2 |
> On Thursday 24 November 2005 12:31, Diego 'Flameeyes' Pettenò wrote: |
3 |
> > What I'm waiting for now are comments if someone has ideas where to |
4 |
> > put guides that does not belong directly to an existant project. And |
5 |
> > if someone wants to join the effort of documenting maintenance |
6 |
> > process for his packages, it would be helpful, too. |
7 |
> |
8 |
> Trying not to let this idea die, as I still think it might be good in |
9 |
> the long run, especially if there's a way to get them collected in a |
10 |
> single place. Right now the main problem is that they are spread across |
11 |
> projects (at least video/sound projects). |
12 |
> |
13 |
> Possible solutions I thought of: |
14 |
> |
15 |
> 1) have every herd controlled by a project, so that the maintainers' |
16 |
> guides can be committed there; it would be difficult to find the |
17 |
> maintainer's guide for a package this way; |
18 |
> 2) have a single repository for maintainers' guides that does not |
19 |
> belong to other projects; |
20 |
> 3) have a single repository for *every* maintainers' guide. |
21 |
> |
22 |
> The problem with 1 and 2 is that the maintainers' guides would be |
23 |
> difficult to locate in the mess of projects. The problem of 3 is that |
24 |
> we have already complex maintainers' guides such as xine's and the one |
25 |
> spyderous wrote for X11 herd, that might be difficult to fit in a |
26 |
> single organization.. |
27 |
> |
28 |
I agree with you. Although it is straightforward to provide a reverse |
29 |
mapping from packages to herds to projects, that currently doesn't exist. |
30 |
|
31 |
> To solve 1's and 2's problem, the solution could be adding a |
32 |
> <maintainerguide> tag to metadata.xml, that carries the URL to the |
33 |
> maintainer's guide for the package. It would also make simpler, for |
34 |
> example, the case where a single guide is used for more than one |
35 |
> package (see always xine's). |
36 |
|
37 |
In any way I like the idea to add a tag to the metadata.xml files. I would |
38 |
however want to do it differently. I'd like to propose a general <doc> |
39 |
tag with the usual attributes (version/deprange, language) and as new |
40 |
attributes a "src" and a "kind" attribute. For your case it would then |
41 |
be: |
42 |
|
43 |
<doc xml:lang="en_EN" src="/proj/en/audio/xine-maint.xml" |
44 |
kind="maintainerguide"/> |
45 |
|
46 |
This way other gentoo (and other) documentation could be linked to the |
47 |
package. |
48 |
|
49 |
Paul |
50 |
|
51 |
ps. We might even link to external (upstream) documentation, and have |
52 |
packages.gentoo.org provide that info. |
53 |
|
54 |
-- |
55 |
Paul de Vrieze |
56 |
Gentoo Developer |
57 |
Mail: pauldv@g.o |
58 |
Homepage: http://www.devrieze.net |