| 1 |
Neil Bothwick wrote: |
| 2 |
> On Wed, 22 Jun 2011 08:27:11 -0500, Dale wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>>> That's because those are global flags. If you set package-specific |
| 6 |
>>> flags in /etc/portage/package.use, eix-test-obsolete will tell you |
| 7 |
>>> when entries can be removed. |
| 8 |
>>> |
| 9 |
> |
| 10 |
>> But when something new comes out, I usually want to add it for all the |
| 11 |
>> packages. I have a few things listed in package.use but I don't want |
| 12 |
>> to clutter the crap out of it and then have two files that needs |
| 13 |
>> cleaning. |
| 14 |
>> |
| 15 |
> Use a directory for package.use, it makes it far easier to manage. All |
| 16 |
> of /etc/portage/package.* are directories here. |
| 17 |
> |
| 18 |
> |
| 19 |
|
| 20 |
I have done that for package.keywords and unmask. In ways it is easier |
| 21 |
but in ways, it is a nightmare. If something is unmasked, I have to go |
| 22 |
find the file that unmasked it. I have several since I use autounmask |
| 23 |
for most of it. Then add in that the new autounmask part of emerge |
| 24 |
seems to pick a random file to add too. At that point, not much makes |
| 25 |
sense anymore. |
| 26 |
|
| 27 |
< sighs > I don't think there is any really easy way to do this except |
| 28 |
to just run stable. o_O |
| 29 |
|
| 30 |
Dale |
| 31 |
|
| 32 |
:-) :-) |
Archives