| 1 |
On Wednesday 22 June 2005 05:28, Jason Stubbs wrote: |
| 2 |
> On Tuesday 21 June 2005 14:35, Alin Nastac wrote: |
| 3 |
> > This would be fine as long as LINGUAS do not appear in IUSE. When |
| 4 |
> > LINGUAS var is empty, the "equery uses" report would be an abomination . |
| 5 |
> |
| 6 |
> The whole point is to add this stuff to IUSE and improve the output |
| 7 |
> accordingly. Using current tools as a reason to not improve things isn't |
| 8 |
> really logical. |
| 9 |
|
| 10 |
And here's a messy patch that took me ten minutes (after looking at equery |
| 11 |
code for the first time) that does just that. Output as follows: |
| 12 |
|
| 13 |
$ ./equery uses portage |
| 14 |
... |
| 15 |
[ Found these USE variables for sys-apps/portage-2.0.51.22-r1 ] |
| 16 |
U I |
| 17 |
- - build : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for |
| 18 |
creating build images and the first half of bootstrapping. |
| 19 |
- - selinux : !!internal use only!! Security Enhanced Linux support, this |
| 20 |
must be set by the selinux profile or breakage will occur |
| 21 |
|
| 22 |
$ ./equery vars portage |
| 23 |
... |
| 24 |
[ Found these environment variables for sys-apps/portage-2.0.51.22-r1 ] |
| 25 |
U I |
| 26 |
----- LINGUAS |
| 27 |
+ + en : <unknown> |
| 28 |
- - fr : <unknown> |
| 29 |
+ + ja : <unknown> |
| 30 |
|
| 31 |
|
| 32 |
Regards, |
| 33 |
Jason Stubbs |
Archives