On Sun, 30 Dec 2012 14:07:04 +0100 Alexander Berntsen <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 30/12/12 13:15, Nuno J. Silva wrote: > > I see his point that emerge will sort of imply what does bindist > > do, but it requires running emerge several times with different USE > > flag combinations, while just writing a small explanation wouldn't > > hurt and would save a lot of time. > You can't check in advance what's going on except for maybe reading > the ebuild. Maybe you could suggest a nice beforehand UI for REQUIRED_USE constraints. > If you happen to have the constraints satisfied for some > reason, you will never even get an error. Meaning you can redistribute the binary. > Furthermore, just *why* is > the constraint there? Patent infringement? Licence incompatibility? Because you can't redistribute the binary if the constraint is not satisfied :) > Etc. ffmpeg is like the holy grail of local bindist descriptions. bindist does absolutely nothing by itself there. do you really want a description like "Enforces license compatibility constraints" ? I consider this a subset of the current bindist description. If you don't then maybe the bindist description should be updated. A.
