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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dne 31.3.2011 06:55, Jeroen Roovers napsal(a):
> On Wed, 23 Mar 2011 01:42:51 +0100
> Tomáš Chvátal wrote:
>
>> Again the diff is: http://tinyurl.com/62eb88b
>
> Why not attach it? What the hell does that URL lead me to?
>
>
> jer
>
Because
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
On Wed, 23 Mar 2011 01:42:51 +0100
Tomáš Chvátal wrote:
> Again the diff is: http://tinyurl.com/62eb88b
Why not attach it? What the hell does that URL lead me to?
jer
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
On Wed, 30 Mar 2011 07:00:21 -0400
"Aaron W. Swenson" wrote:
> As for the lib_dir(), I'm unsure if that's a good way to handle things.
> Or, if it's really the best way, even though it's ugly. There's nothing
> preventing me from making it a user configurable...it's just that at
> some point I do
-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.
>
On Wed, Mar 30, 2011 at 01:27:48PM +0300, Samuli Suominen wrote:
>
> That said, I still support the idea of news item, just not the idea of
> you trying to dump the responsibility from the desktop maintainers to me...
>
> - Samuli
>
That wasn't my attempt at all. I am sorry if I expressed in a
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
On 30/03/2011 16:12, Tomas Chvatal (scarabeus) wrote:
> scarabeus11/03/30 14:12:55
>
> Modified: ChangeLog rsyslog-5.6.5.ebuild rsyslog-5.6.4.ebuild
> Log:
> Drop logrotate useflag. Fixes bug #344175.
>
> (Portage version: 2.2.0_alpha29/cvs/Linux x86_64)
>
> Revision Cha
> "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 Monday, March 28, 2011 08:26:00 AM Tomáš Chvátal wrote:
> So after bit of smashing here and there the list of packages depending
> on media-libs/ffmpeg is stored and automatically generated on my reports
> page [1] (automatic generation is working if i didn't screw up once a day).
>
> So if you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/30/2011 03:58 AM, Fabian Groffen wrote:
> On 29-03-2011 22:35:48 -0600, Ryan Hill wrote:
>>> Because 'ls' would complain that files didn't exist, such as lib*.dylib
>>> when on a Linux system. It doesn't matter. But, using 'find' avoids this
>>
On 03/30/2011 01:36 AM, Markos Chandras wrote:
> On Sun, Mar 27, 2011 at 11:36:00AM +0300, Samuli Suominen wrote:
>> USE="hal" is masked in base/use.mask, but unmasked for kde-base/solid
>> and app-cdr/k3b in base/package.use.mask pending on KDE 4.6.x stabilization.
>>
>
> Why didn't you use the n
I recently saw:
http://bugs.gentoo.org/show_bug.cgi?id=360445
dev-dotnet/gnome-sharp seems to require avahi even if it shouldn't. I
have seen that it also affects to other packages like
gnome-base/libgnome. This also sounds me a bit like:
http://bugs.gentoo.org/show_bug.cgi?id=343841
How should I
Le mardi 29 mars 2011 à 23:36 +0100, Markos Chandras a écrit :
> On Sun, Mar 27, 2011 at 11:36:00AM +0300, Samuli Suominen wrote:
> > USE="hal" is masked in base/use.mask, but unmasked for kde-base/solid
> > and app-cdr/k3b in base/package.use.mask pending on KDE 4.6.x stabilization.
> >
> > This
On 29-03-2011 22:35:48 -0600, Ryan Hill wrote:
> > Because 'ls' would complain that files didn't exist, such as lib*.dylib
> > when on a Linux system. It doesn't matter. But, using 'find' avoids this
> > mess.
>
> Never use ls to get filenames in a script. Instead of
>
> for link_source in $(
22 matches
Mail list logo