| 1 |
On Mon, 23 Jan 2017 18:37:15 +0100 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
> > For example, if you allow use.mask or use.force in mixins, you can |
| 4 |
> > end up having unsatisfiable deps that repoman will never catch. |
| 5 |
> > Arguably, desktop profiles relying on having an useflag forced on a |
| 6 |
> > given package are already semi-broken: they'd be better with the |
| 7 |
> > useflag default enabled and proper usedeps, so the mask/force game |
| 8 |
> > doesnt seem really useful for mixins. |
| 9 |
> |
| 10 |
> That's why if you do such a thing, you would have to declare a regular |
| 11 |
> profile using this mix-in for repoman to test. |
| 12 |
> |
| 13 |
|
| 14 |
still that doesn't account for a 'ihatelennart' mixin masking udev & |
| 15 |
systemd and a 'ilovelennart' mixin masking udev & eudev and an user |
| 16 |
enabling them both |
| 17 |
|
| 18 |
why not let such a stupid example be, it is similar to package.mask |
| 19 |
users can already fill, but I'm pretty sure more subtle breakage will |
| 20 |
appear |
| 21 |
|
| 22 |
repoman will test n out of 2^n (or n!) possibilities the way you |
| 23 |
suggest, which is basically nothing when n is big |
Archives