On Sat, Dec 29, 2012 at 6:54 PM, Alexander Berntsen <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > All packages should have local descriptions of what the bindist > USE-flag specifically does. This should be a policy when writing > ebuilds that include it. > ... > I have filed bug reports for the affected packages. However, to avoid > this becoming an issue in the future I think it would be fruitful to > have a policy or something to make sure all ebuilds that make use of the > bindist USE-flag at the very least describe *what* toggling it does in > the context of that specific package, and preferably also *why* the > flag exists in the first place. This will summarise the problem and > the solution that USE=+bindist offers for the end-user. I don't find > it acceptable to make the details "left as an exercise" to the user.
Once all packages currently using the flag have local descriptions, we could remove bindist from profiles/use.desc, converting it from a global to a local use flag. This would cause repoman to reject any new instances without a local description. That would be much more effective than a policy that may be (accidentally) ignored.
