| 1 |
All the more reason to build the docs from the code directly with doxygen or |
| 2 |
whatever. I'm pretty sure nobody writes code with the intent it doesn't get |
| 3 |
used, from a coder standpoint having documentation helps feature acceptance. |
| 4 |
|
| 5 |
This feature probably is documented but since I can't find that documentation |
| 6 |
quickly (i.e. just could find it in under 5 minutes) it might as well not |
| 7 |
exist to the majority of devs. We s'port too many hidden feats. |
| 8 |
|
| 9 |
Anyway we've got lots of docs but were lacking a good taxonomy for them, do we |
| 10 |
have any librarians helping the docs team? (cc'ing doc to get a reply about |
| 11 |
this) |
| 12 |
|
| 13 |
So let me rephrase that portage docs need to be complete and up to date at all |
| 14 |
times (at least an english version, devs should know enough english). Linking |
| 15 |
the documentation to the code is the only way I can see this happen. |
| 16 |
|
| 17 |
Bart. |
| 18 |
|
| 19 |
On Monday 29 December 2003 00:02, Daniel Robbins wrote: |
| 20 |
> |
| 21 |
> This results in the current USE settings. I do think that not too many |
| 22 |
> people know about auto-USE, so it is somewhat under-utilized. |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-portage-dev@g.o mailing list |
Archives