1 |
On 12/18/05, Xavier Neys <neysx@g.o> wrote: |
2 |
> pclouds wrote: |
3 |
> > Hi, |
4 |
> > While translating documents, i found that several documents have not |
5 |
> > updated to reflect current packages in portage (sorry i forgot most of |
6 |
> > them). |
7 |
> |
8 |
> That's not very helpful then. |
9 |
> If you find that a doc that needs to be fixed, it needs to be fixed, as simple |
10 |
> as that. Please file a bug, a patch, send a mail, whatever. |
11 |
Ok, so here what i've still remembered: |
12 |
- colinux-howto.xml needs to be updated. It uses 2.4 and said that |
13 |
2.6 is not possible. 2.6 is possible now. Also there is another way to |
14 |
setup networking in colinux (as described in |
15 |
http://wiki.colinux.org/cgi-bin/coLinuxNetworking#head-50014b6fc00ec98d0eaac65e39346e5bbfe41a37) |
16 |
- gentoo-kernel.xml: please remove gentoo-dev-sources and updated |
17 |
other sources if needed (i don't use them so i can't tell) |
18 |
- utf-8.xml said that nano does not support utf-8 but i heard in |
19 |
gentoo-dev that nano has supported utf-8. Please verify. |
20 |
|
21 |
|
22 |
|
23 |
> |
24 |
> > I would like to suggest making a link between a document and |
25 |
> > relevant packages. Then we could encourage devs to check these |
26 |
> > documents when they update packages and suggest doc team to fix docs. |
27 |
> > It'd also be useful for users if we publish these info on |
28 |
> > packages.g.o, show links to documents revelant to packages. |
29 |
> > These info could be stored in package's metadata.xml (for example |
30 |
> > alsa* package's metadata.xml would have a link to alsa-guide.xml). |
31 |
> > Category's metadata.xml could be used too (for example, |
32 |
> > sys-kernel/metadata.xml should contain a link to kernel-guide.xml, |
33 |
> > this document need to be updated really, gentoo-dev-sources have died |
34 |
> > for months and should be removed from the doc). |
35 |
> > I'd like to know doc team's comment first before post it to |
36 |
> > gentoo-dev. Any comment? |
37 |
> |
38 |
> Adding a <doc> tag to metadata.xml has been discussed recently on -dev. |
39 |
> Once the guys in charge of metadata.xml have implemented support for it, and |
40 |
> once the devs have added the info to their packages' metadata.xml, and once |
41 |
> the guys in charge of p.g.o use it, it will magically work. |
42 |
> None of that is in the hands of GDP. |
43 |
|
44 |
If <doc> was added to metadata.dtd, who would be responsible for |
45 |
maintaining it? Ebuild maintainers or doc team? |
46 |
-- |
47 |
Bi Cờ Lao |
48 |
|
49 |
-- |
50 |
gentoo-doc@g.o mailing list |