2011/3/31 Tomáš Chvátal :
> Well technically yep, but for lets say the ffmpeg the mp3 useflag means
> "Enable mp3 encoding support." :)
>
> If user sets -mp3 it still can play mp3 tracks but in really worse
> quality so it is just nice convinience that ffmpeg always allows playing
> those files.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dne 31.3.2011 09:51, Fabian Groffen napsal(a):
> On 31-03-2011 09:41:10 +0200, Tomáš Chvátal wrote:
>> Dne 31.3.2011 09:33, Fabian Groffen napsal(a):
>>> On 31-03-2011 09:23:16 +0200, justin wrote:
instead of the default
mp3 - Add suppor
On 31/03/11 09:57, Fabian Groffen wrote:
> On 31-03-2011 09:44:37 +0200, justin wrote:
>> First is a package specific, second is the default.
>>
>> And no, asuming the USE is introduced correctly here, it makes a
>> difference, whether we take the global meaning -> reading mp3 files at
>> all; or c
On 31-03-2011 09:44:37 +0200, justin wrote:
> First is a package specific, second is the default.
>
> And no, asuming the USE is introduced correctly here, it makes a
> difference, whether we take the global meaning -> reading mp3 files at
> all; or changing the way it is done for this package. Be
On 31-03-2011 09:41:10 +0200, Tomáš Chvátal wrote:
> Dne 31.3.2011 09:33, Fabian Groffen napsal(a):
> > On 31-03-2011 09:23:16 +0200, justin wrote:
> >> instead of the default
> >>
> >> mp3 - Add support for reading mp3 files
> >
> > I find the default clear enough. It seems the mp3 USE-flag is
>
On 31/03/11 09:33, Fabian Groffen wrote:
> On 31-03-2011 09:23:16 +0200, justin wrote:
>> This is what I mean by good description
>>
>> +Enable support for mp3 decoding over
>> media-sound/mpg123 instead of relying on ffmpeg support.
>>
>> instead of the default
>>
>> mp3 - Add support for read
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dne 31.3.2011 09:33, Fabian Groffen napsal(a):
> On 31-03-2011 09:23:16 +0200, justin wrote:
>> This is what I mean by good description
>>
>> +Enable support for mp3 decoding over
>> media-sound/mpg123 instead of relying on ffmpeg support.
>>
>> in
On 31-03-2011 09:23:16 +0200, justin wrote:
> This is what I mean by good description
>
> + Enable support for mp3 decoding over
> media-sound/mpg123 instead of relying on ffmpeg support.
>
> instead of the default
>
> mp3 - Add support for reading mp3 files
>
> Everybody understands what m
This is what I mean by good description
+ Enable support for mp3 decoding over
media-sound/mpg123 instead of relying on ffmpeg support.
instead of the default
mp3 - Add support for reading mp3 files
Everybody understands what mp3 means, but we truely need something else
here.
justin
s
2011/3/31 Eray Aslan :
> On Wed, Mar 30, 2011 at 04:41:25PM -0500, Dale wrote:
>> +1 Some descriptions may as well not have one at all. May as well
>> Google the flag and the package and see what, if anything, it returns.
>
> I would say working as intended. If you do not know what a package
> d
Amadeusz Żołnowski wrote:
Excerpts from Alec Warner's message of Thu Mar 31 08:23:45 +0200 2011:
On Thu, Mar 31, 2011 at 5:59 AM, Dale wrote:
Eray Aslan wrote:
In all seriousness, this has been discussed before and it doesn't
get any better. I'm not sure how to fix it either. The s
Excerpts from Alec Warner's message of Thu Mar 31 08:23:45 +0200 2011:
> On Thu, Mar 31, 2011 at 5:59 AM, Dale wrote:
> > Eray Aslan wrote:
> > In all seriousness, this has been discussed before and it doesn't
> > get any better. I'm not sure how to fix it either. The space for
> > the descripti
On Thu, Mar 31, 2011 at 5:59 AM, Dale wrote:
> Eray Aslan wrote:
>>
>> On Wed, Mar 30, 2011 at 04:41:25PM -0500, Dale wrote:
>>
>>>
>>> +1 Some descriptions may as well not have one at all. May as well
>>> Google the flag and the package and see what, if anything, it returns.
>>>
>>
>> I would s
Eray Aslan wrote:
On Wed, Mar 30, 2011 at 04:41:25PM -0500, Dale wrote:
+1 Some descriptions may as well not have one at all. May as well
Google the flag and the package and see what, if anything, it returns.
I would say working as intended. If you do not know what a package
does,
On Wed, Mar 30, 2011 at 04:41:25PM -0500, Dale wrote:
> +1 Some descriptions may as well not have one at all. May as well
> Google the flag and the package and see what, if anything, it returns.
I would say working as intended. If you do not know what a package
does, chances are you don't need
Aaron W. Swenson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/30/2011 05:41 PM, Dale wrote:
Amadeusz Żołnowski wrote:
Justin has pointed problem which is worth our attention. It is not just
me being pissed off when reading „Enable support for foo”, there are
many user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/30/2011 05:41 PM, Dale wrote:
> Amadeusz Żołnowski wrote:
>> Justin has pointed problem which is worth our attention. It is not just
>> me being pissed off when reading „Enable support for foo”, there are
>> many users complaining about that.
>
Amadeusz Żołnowski wrote:
Justin has pointed problem which is worth our attention. It is not just
me being pissed off when reading „Enable support for foo”, there are
many users complaining about that.
+1 Some descriptions may as well not have one at all. May as well
Google the flag and
Excerpts from Olivier Crête's message of Wed Mar 30 22:14:30 +0200 2011:
> On Wed, 2011-03-30 at 21:56 +0200, Amadeusz Żołnowski wrote:
> > The main problem is that user might not know what kind of “foo” support
> > it is. For example I have “pango” USE flag in sys-boot/plymouth. What
> > would exp
On Wed, 2011-03-30 at 21:56 +0200, Amadeusz Żołnowski wrote:
> The main problem is that user might not know what kind of “foo” support
> it is. For example I have “pango” USE flag in sys-boot/plymouth. What
> would explain to you something like: “Enables support for
> x11-libs/pango”? And how you w
Excerpts from James Cloos's message of Wed Mar 30 18:13:21 +0200 2011:
> j> Enables foo intergration
> j> or
> j> Enables support for foo
>
> j> if it isn't totally clear what "foo" is
>
> Even preferring $C/$PN where $PN is currently used would help,
> since it makes it clear that the foo is a p
> "j" == justin writes:
j> In my opinion some thing like
j> Enables foo intergration
j> or
j> Enables support for foo
j> if it isn't totally clear what "foo" is
Even preferring $C/$PN where $PN is currently used would help,
since it makes it clear that the foo is a package.
-JimC
--
Jam
On 29/03/11 18:02, Andy Spencer wrote:
> On 2011-03-29 17:10, Jeroen Roovers wrote:
>> You could start by pointing out some good examples of bad
>> descriptions.
>
> A few regular expressions might help with that:
>
> /:(\w+) - (Enable|Add) support for \1$/
> /:(\w+) - (Enable|Add) \1( suppor
On Tue, Mar 29, 2011 at 10:30 PM, Matt Turner wrote:
> One USE flag I remember in particular bothering me was
> gnome-extra/gnome-games' guile USE flag.
>
> The global description says "guile - Adds support for the guile Scheme
> interpreter" but this flag is actually determines whether a number o
On Tue, Mar 29, 2011 at 2:24 PM, justin wrote:
> Hi,
>
> the descriptions of USE flags should explain what the USE is good for.
> In my opinion some thing like
>
> Enables foo intergration
> or
> Enables support for foo
>
> if it isn't totally clear what "foo" is, sucks!! There are many, many
> de
Le mardi 29 mars 2011 à 16:02 +, Andy Spencer a écrit :
>
> app-office/abiword-plugins:thesaurus - Enable thesaurus support
> app-office/abiword:thesaurus - Enable thesaurus support
can't help you if you don't know what a thesaurus is, really :(
--
Gilles Dartiguelongue
Gentoo
On 2011-03-29 17:10, Jeroen Roovers wrote:
> You could start by pointing out some good examples of bad
> descriptions.
A few regular expressions might help with that:
/:(\w+) - (Enable|Add) support for \1$/
/:(\w+) - (Enable|Add) \1( support)?$/
For example:
app-admin/puppet:shadow - Enab
Excerpts from Angelo Arrifano's message of Tue Mar 29 17:14:48 +0200 2011:
> On Ter, 2011-03-29 at 17:08 +0200, Amadeusz Żołnowski wrote:
> > I'm actually describing even global USE flags in my package's
> > metadata.xml if their purpose might not be clear and I'd like to
> > expect that from other
On Ter, 2011-03-29 at 17:08 +0200, Amadeusz Żołnowski wrote:
> Excerpts from justin's message of Tue Mar 29 16:24:57 +0200 2011:
> > the descriptions of USE flags should explain what the USE is good for.
> > In my opinion some thing like
> >
> > Enables foo intergration
> > or
> > Enables support
On Tue, 29 Mar 2011 16:24:57 +0200
justin wrote:
> if it isn't totally clear what "foo" is, sucks!!
You could start by pointing out some good examples of bad descriptions.
> So please enhance you descriptions!!
And when you do, also remove all exclamation marks. Not all Gentoo
users are used t
Excerpts from justin's message of Tue Mar 29 16:24:57 +0200 2011:
> the descriptions of USE flags should explain what the USE is good for.
> In my opinion some thing like
>
> Enables foo intergration
> or
> Enables support for foo
>
> if it isn't totally clear what "foo" is, sucks!! There are man
Hi,
the descriptions of USE flags should explain what the USE is good for.
In my opinion some thing like
Enables foo intergration
or
Enables support for foo
if it isn't totally clear what "foo" is, sucks!! There are many, many
description which do not tell me as a user without googling what I co
32 matches
Mail list logo
