On 31/12/2012 14:28, Nuno J. Silva wrote:
>"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)."
Congrats for missing the poi
On Sun, 30 Dec 2012 15:15:25 +0100
Michał Górny wrote:
> On Sun, 30 Dec 2012 11:01:52 -0300
> Alexis Ballier 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 "Enfo
On Sun, 30 Dec 2012 15:10:21 +0100
Alexander Berntsen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 30/12/12 15:01, Alexis Ballier wrote:
> > Maybe you could suggest a nice beforehand UI for REQUIRED_USE
> > constraints.
> I think this is orthogonal to the discussion. If ffm
On Sun, 30 Dec 2012 11:01:52 -0300
Alexis Ballier 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/12/12 15:01, Alexis Ballier wrote:
> Maybe you could suggest a nice beforehand UI for REQUIRED_USE
> constraints.
I think this is orthogonal to the discussion. If ffmpeg had a local
description of bindist,
# equery u ffmpeg
would outpu
On Sun, 30 Dec 2012 14:07:04 +0100
Alexander Berntsen 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 US
-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
> hu
