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( support)?$/
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 $(eval ls
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 is
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
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 news
-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
mess.
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
j == justin j...@gentoo.org 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
--
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 Changes
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 package.
The
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
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 explain
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
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 wrong
-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, 30 Mar 2011 07:00:21 -0400
Aaron W. Swenson titanof...@gentoo.org 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
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
On Wed, 23 Mar 2011 01:42:51 +0100
Tomáš Chvátal scarab...@gentoo.org wrote:
Again the diff is: http://tinyurl.com/62eb88b
Why not attach it? What the hell does that URL lead me to?
jer
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
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,
20 matches
Mail list logo