| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Alec Warner wrote: |
| 5 |
> Zac Medico wrote: |
| 6 |
> |
| 7 |
>> Users can unforce them via /etc/portage/profile/{use.force,package.use.force} in the usual "-flag" way. |
| 8 |
> |
| 9 |
> Why new files? Why isn't this just pushed into the use stacking order |
| 10 |
> over-ridable by the user (default USE flags, and not forcing)? |
| 11 |
|
| 12 |
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. |
| 13 |
|
| 14 |
> Then they can over-ride it in package.use just like they do now? |
| 15 |
|
| 16 |
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). |
| 17 |
|
| 18 |
Zac |
| 19 |
-----BEGIN PGP SIGNATURE----- |
| 20 |
Version: GnuPG v1.4.5 (GNU/Linux) |
| 21 |
|
| 22 |
iD8DBQFE153K/ejvha5XGaMRAoGnAJ9sCh9OMu064tLwScuyQdBvbHiwKwCg3RBv |
| 23 |
4feX6Eg2jZen/TiQfhdzr6o= |
| 24 |
=j/9F |
| 25 |
-----END PGP SIGNATURE----- |
| 26 |
-- |
| 27 |
gentoo-portage-dev@g.o mailing list |
Archives