| 1 |
Zac Medico wrote: |
| 2 |
> Alec Warner wrote: |
| 3 |
>>> Zac Medico wrote: |
| 4 |
>>> |
| 5 |
>>>> Users can unforce them via /etc/portage/profile/{use.force,package.use.force} in the usual "-flag" way. |
| 6 |
>>> Why new files? Why isn't this just pushed into the use stacking order |
| 7 |
>>> over-ridable by the user (default USE flags, and not forcing)? |
| 8 |
> |
| 9 |
> Much like use.mask, which is for flags that almost certainly should _not_ be enabled, use.force is for flags that almost certainly _should_ enable. |
| 10 |
> |
| 11 |
>>> Then they can over-ride it in package.use just like they do now? |
| 12 |
> |
| 13 |
> Again, it's akin to use.mask, and protects the user from accidentally doing something that they almost certainly shouldn't do (though they have the option to override it if absolutely necessary). |
| 14 |
> |
| 15 |
> Zac |
| 16 |
|
| 17 |
hrm, so not default use flags then. |
| 18 |
-- |
| 19 |
gentoo-portage-dev@g.o mailing list |
Archives