| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
El Jue 09 May 2002 18:06, Bob Phan escribió: |
| 5 |
> I think it would be a good idea for someone (I could do this if no one |
| 6 |
> wants to) to maintain a parsable list of all the use variables, what |
| 7 |
> they are for, and which ebuilds use them. This would be useful for |
| 8 |
> writing tools that would want to know this information, or even for |
| 9 |
> automatic maintenence of a webpage for use variables. CSV or XML |
| 10 |
> would be a good format for this. XML may be overkill, expecially for |
| 11 |
> someone wanting to write a shell script with acess to this |
| 12 |
> information, but XML would also work great for c, perl, python, and |
| 13 |
> web maintenence. |
| 14 |
> |
| 15 |
> I have taken a look at /usr/portage/profiles/use.desc, |
| 16 |
> and while useful for users to read, it is not easily parsable. |
| 17 |
> |
| 18 |
> Any thoughts, suggestions? |
| 19 |
|
| 20 |
and... going on work... we could make the same to the commands of the ebuild |
| 21 |
packages, like dodir, doins, and those... to get them well-documented and in |
| 22 |
an ordered way... |
| 23 |
|
| 24 |
|
| 25 |
Greetins |
| 26 |
-----BEGIN PGP SIGNATURE----- |
| 27 |
Version: GnuPG v1.0.7 (GNU/Linux) |
| 28 |
|
| 29 |
iD8DBQE82uEmAE7Ivj6LuFMRAvg6AKCbC3VCVRXC3CgM2r4edmb3lRBilQCdGiV3 |
| 30 |
EJHmb4b6nX2iEnnT7yOhMO0= |
| 31 |
=ukrR |
| 32 |
-----END PGP SIGNATURE----- |
Archives