From: nunojsilva@ist.utl.pt (Nuno J. Silva)
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Local bindist descriptions
Date: Mon, 31 Dec 2012 15:28:53 +0200 [thread overview]
Message-ID: <874nj273l6.fsf@ist.utl.pt> (raw)
In-Reply-To: 20121231064355.0ba23b07@portable
On 2012-12-31, Alexis Ballier wrote:
> On Sun, 30 Dec 2012 15:15:25 +0100
> Michał Górny <mgorny@gentoo.org> wrote:
>
>> On Sun, 30 Dec 2012 11:01:52 -0300
>> Alexis Ballier <aballier@gentoo.org> wrote:
>>
>> > > 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.
>>
>> Well, that's another problem we have there. I really like the ffmpeg
>> idea of 'bindist' not doing anything by itself. If all packages did
>> that, I would see no problem with having global meaningful 'bindist'.
>>
>> But if in some cases USE=bindist does something, then I believe ffmpeg
>> should describe that it just 'enforces REQUIRED_USE contraints' with
>> no hidden magic beneath.
>
> Yep you're right, I guess in that case it's good to add such a
> description.
And maybe "check ebuild for more information", although I think this is
rather suboptimal approach, if we're providing a description for it, we
may as well provide a more complete one, and, for the same cost, make
life easier for other people:
"Do not allow the compilation of patent-encumbered AAC
encoders. Please note that disabling this flag does not enable these
features, which are ruled by separate flags (encoding and either faac
or aacplus)."
--
Nuno Silva (aka njsg)
http://njsg.sdf-eu.org/
next prev parent reply other threads:[~2012-12-31 13:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50DCAF67.90907@plaimi.net>
2012-12-29 23:54 ` [gentoo-dev] Local bindist descriptions Alexander Berntsen
2012-12-30 2:49 ` Matt Turner
2012-12-30 3:03 ` Mike Gilbert
2012-12-30 11:39 ` Diego Elio Pettenò
2012-12-30 11:42 ` Alexander Berntsen
2012-12-30 14:04 ` Alexis Ballier
2013-01-02 17:58 ` Cyprien Nicolas
2013-01-02 19:35 ` Mike Frysinger
2012-12-30 12:15 ` [gentoo-dev] " Nuno J. Silva
2012-12-30 13:07 ` Alexander Berntsen
2012-12-30 14:01 ` Alexis Ballier
2012-12-30 14:10 ` Alexander Berntsen
2012-12-30 14:32 ` Alexis Ballier
2012-12-30 14:15 ` Michał Górny
2012-12-31 9:43 ` Alexis Ballier
2012-12-31 13:28 ` Nuno J. Silva [this message]
2012-12-31 13:27 ` Diego Elio Pettenò
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874nj273l6.fsf@ist.utl.pt \
--to=nunojsilva@ist.utl.pt \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox