| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
|
| 5 |
Hi |
| 6 |
> > well-documented and in an ordered way... |
| 7 |
> |
| 8 |
> I don't follow? The goal isn't to make an xml ebuild, as I rather |
| 9 |
> like them as shell scripts and it lowers the bar a little for people |
| 10 |
> that wan't to start writing their own. The design goels for what I |
| 11 |
> suggested, is basically a way to keep track of all currently used USE |
| 12 |
> vars. And basically, three things are important about each. |
| 13 |
> |
| 14 |
> 1) What they are called. |
| 15 |
> 2) What they mean. |
| 16 |
> 3) Which packages use them. |
| 17 |
> |
| 18 |
> I think it would be a valuable resource to have a maintainable and |
| 19 |
> parsable list of these. As it stands, I already have a perl script |
| 20 |
> that can dig out 1 & 2 and dump them into XML. I'm going to tidy it |
| 21 |
> up a bit and probably post it to this group. |
| 22 |
ups... excuseme... I have reread the msg. and I'm with you either ;) |
| 23 |
So... when do we begin ? |
| 24 |
|
| 25 |
Greets |
| 26 |
-----BEGIN PGP SIGNATURE----- |
| 27 |
Version: GnuPG v1.0.7 (GNU/Linux) |
| 28 |
|
| 29 |
iD8DBQE82ukvAE7Ivj6LuFMRAhjDAJ4vFn7uSLM6I7+D8RJhJBIdybKdhACgrzZK |
| 30 |
6lcjS+yxMVyWlt/0I1Cyoww= |
| 31 |
=lgk6 |
| 32 |
-----END PGP SIGNATURE----- |
Archives