| 1 |
Matt Turner wrote: |
| 2 |
> I think in large part recently it's because of use.stable.mask and |
| 3 |
> package.use.stable.mask. These really are a nightmare for users. |
| 4 |
.. |
| 5 |
> I think most of the confusion is caused by the necessity to put a |
| 6 |
> *stable* package atom into package.keywords to unmask a *USE* flag. |
| 7 |
|
| 8 |
A lot can be learned just from the filenames: |
| 9 |
|
| 10 |
use.stable.mask |
| 11 |
package.use.stable.mask |
| 12 |
|
| 13 |
The latter indicates that this concept has no less than four dimensions. |
| 14 |
|
| 15 |
Let's enumerate and associate: |
| 16 |
|
| 17 |
1. use - USE flags - no problem, Gentoo users either love USE flags or leave |
| 18 |
2. stable - arch vs. ~arch - no problem, even installation docs describe it |
| 19 |
3. mask - masked packages - OK, at some point people encounter masked packages |
| 20 |
4. package - per-package stuff - like with /etc/portage/package.use |
| 21 |
|
| 22 |
How stable and mask interact with USE is absolutely unclear and usability |
| 23 |
of this is very close to zero. |
| 24 |
|
| 25 |
|
| 26 |
//Peter |
Archives