Re: [gentoo-dev] Local bindist descriptions
Alexis Ballier wrote: It's probably too idealistic but I tend to consider that global flags should be enabled/disabled globally while local flags on a per-package basis. bindist is really something you want to enable globally. On the other hand, doc is a global flag you don't want to enable globally. -- Cyprien (Fulax)
Re: [gentoo-dev] Local bindist descriptions
On Wednesday 02 January 2013 12:58:01 Cyprien Nicolas wrote: Alexis Ballier wrote: It's probably too idealistic but I tend to consider that global flags should be enabled/disabled globally while local flags on a per-package basis. bindist is really something you want to enable globally. On the other hand, doc is a global flag you don't want to enable globally. or vanilla or debug or examples ... i'm sure there are others too -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Local bindist descriptions
On 30/12/2012 04:03, Mike Gilbert wrote: That would be much more effective than a policy that may be (accidentally) ignored. +1 -- Diego Elio Pettenò — Flameeyes flamee...@flameeyes.eu — http://blog.flameeyes.eu/
Re: [gentoo-dev] Local bindist descriptions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/12/12 12:39, Diego Elio Pettenò wrote: On 30/12/2012 04:03, Mike Gilbert wrote: That would be much more effective than a policy that may be (accidentally) ignored. +1 +1 from me as well. A much simpler and reliable way of achieving what I want. - -- Alexander alexan...@plaimi.net http://plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlDgKJ8ACgkQRtClrXBQc7XRqgEAn4IGnXvevFHkfidz6BYwR9lt ZM/s9E1s7pRcbq92RpUA/3DoaKg6qzEKV0VgjVDC9czRfP1eZDU/RYJmXJbpaoqC =drvi -END PGP SIGNATURE-
Re: [gentoo-dev] Local bindist descriptions
On Sun, 30 Dec 2012 12:42:23 +0100 Alexander Berntsen alexan...@plaimi.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/12/12 12:39, Diego Elio Pettenò wrote: On 30/12/2012 04:03, Mike Gilbert wrote: That would be much more effective than a policy that may be (accidentally) ignored. +1 +1 from me as well. A much simpler and reliable way of achieving what I want. It's probably too idealistic but I tend to consider that global flags should be enabled/disabled globally while local flags on a per-package basis. bindist is really something you want to enable globally.
[gentoo-dev] Local bindist descriptions
-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. The bindist USE-flag is for avoiding components in a package that would result in non-re-distributable binary packages. The generic global description is Flag to enable or disable options for prebuilt (GRP) packages (eg. due to licensing issues). This is very vague. It does not in any way explain the specifics of what enabling the flag will do. This means that each package should describe what it specifically does. www-client/firefox-10.0.11 is one example that does this properly with Disable official Firefox branding (icons, name) which are not binary-redistributable according to upstream. This is perfectly descriptive. net-misc/openssh is one example that does not have a local/specific description. To me, this is unacceptable. Someone who cares enough about licensing and distribution etc. to set the bindist USE-flag, will likely care about the specifics of the it as well. Furthermore, different people find different things unacceptable. As an example, patent-encumbered codec support in ffmpeg is something that might be considered unacceptable to some. However, the very same people might not be worried about trademark/branding-related issues, such as is the case with Firefox. This is comparable to how some find the GPL acceptable, but not the Artistic License 1.0, and ebuilds do indeed require the licence -- not LICENSE=free-ish. 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. The affected packages per now* are all versions of: dev-db/libdbi-drivers dev-db/opendbx dev-libs/gf2x gnome-extra/libgda kde-base/oxygen-icons media-libs/freetype media-libs/libaacplus media-libs/mediastreamer media-libs/mesa media-plugins/mediastreamer-silk media-video/ffmpeg media-video/libav media-video/mplayer media-video/mplayer2 net-dialup/freeradius net-libs/gnutls net-libs/liboauth net-misc/openssh net-misc/vpnc sci-visualization/qtiplot Newer versions of gnutls don't have the USE-flag, so I'll let that one slide. ffmpeg is problematic... see: https://bugs.gentoo.org/show_bug.cgi?id=369249. *27/12/12 21:38 - - -- Alexander alexan...@plaimi.net http://plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAlDfgr4ACgkQRtClrXBQc7Uk1wEAjWXbV8bYtsUu6BXFRXhBXcMr 5eEHDbA9BTcXg+ouKsUA/RAKFzGA/gW40oSpJecf3zics7wQ4h7xYhPbbtvGvF9x =xkAA -END PGP SIGNATURE-
Re: [gentoo-dev] Local bindist descriptions
On Sat, Dec 29, 2012 at 3:54 PM, Alexander Berntsen alexan...@plaimi.net wrote: 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. Agreed. media-libs/mesa Fixed. (bug 448932)
Re: [gentoo-dev] Local bindist descriptions
On Sat, Dec 29, 2012 at 6:54 PM, Alexander Berntsen alexan...@plaimi.net 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.
