| 1 |
I suppose we could consider it as a hard vs soft configuration? |
| 2 |
|
| 3 |
hard enable = Enable no matter what, and cause an error |
| 4 |
soft enable = Enable, unless it would break dependency |
| 5 |
soft disable = Disable, unless it would break a dependency |
| 6 |
hard disable = Disable no matter what, and cause an error |
| 7 |
|
| 8 |
On Wed, Feb 10, 2016 at 12:00 PM, Róbert Čerňanský <openhs@×××××××××.com> |
| 9 |
wrote: |
| 10 |
|
| 11 |
> On Wed, 10 Feb 2016 15:23:27 +1300 |
| 12 |
> Kent Fredric <kentfredric@×××××.com> wrote: |
| 13 |
> |
| 14 |
> > >> I'd personally rather the list of "automatically turn this on if |
| 15 |
> > >> required" be something I had the power to restrict than have a |
| 16 |
> > >> blanket "autodostuff", because in the event some USE can't be |
| 17 |
> |
| 18 |
> Although I prefer non-explicit auto/lazy use flags, the explicit |
| 19 |
> approach is also perfectly fine (especially when compared to current |
| 20 |
> situation). In the end I would most certainly be able to specify all |
| 21 |
> use flags as lazy and thus have effectively the same behaviour as with |
| 22 |
> non-explicit approach. |
| 23 |
> |
| 24 |
> > So in comparison: |
| 25 |
> > |
| 26 |
> > /etc/portage/package.use is essentially "the world file but for |
| 27 |
> > useflags" |
| 28 |
> > |
| 29 |
> > And we have no analogue of |
| 30 |
> > |
| 31 |
> > /etc/porage/package.unmask or /etc/portage/package.keywords that |
| 32 |
> > applies to useflags. |
| 33 |
> |
| 34 |
> I find /etc/portage/package.use (or make.conf) analogous to world AND |
| 35 |
> mask files. For packages world + mask files give you possibility to |
| 36 |
> specify which packages you: |
| 37 |
> |
| 38 |
> - want (listed in world file) |
| 39 |
> - don't want (listed in a mask file) |
| 40 |
> - not care (not listed in any of them) |
| 41 |
> |
| 42 |
> (Assuming non-explicit approach) similarly for use flags, package.use |
| 43 |
> or make.conf gives you possibility to specify which use flags you: |
| 44 |
> |
| 45 |
> - want (listed in package.use or make.conf) |
| 46 |
> - don't want (listed with '-' in package.use or make.conf) |
| 47 |
> - not care (not listed in any of them) |
| 48 |
> |
| 49 |
> The advantage of explicit approach could be that even if a use flag is |
| 50 |
> enabled or disabled globally, it would still be possible to make it |
| 51 |
> lazy/automatic for specific packages. |
| 52 |
> |
| 53 |
> > I can see how some people might want an analogue of "just install |
| 54 |
> > dependencies if they're needed regardless if I said I need them" that |
| 55 |
> > applies to useflags, but you'd probably want a "don't install this |
| 56 |
> > even if it appeared to be needed" companion tool that behaves akin to |
| 57 |
> > /etc/portage/package.mask |
| 58 |
> |
| 59 |
> This would be package.use or make.conf. |
| 60 |
> |
| 61 |
> |
| 62 |
> -- |
| 63 |
> Róbert Čerňanský |
| 64 |
> E-mail: openhs@×××××××××.com |
| 65 |
> Jabber: hs@××××××.sk |
| 66 |
> |
| 67 |
> |
Archives