In an attempt to patch all driver packages automatically, I've modified
x-modular.eclass to do something along the lines of what elibtoolize
does for its patching. However, this would require the storage of a
patch for x-modular.eclass, which I would intend to place in a
subdirectory of
On Fri, 09 Dec 2005 12:13:08 -0700 Joshua Baergen
[EMAIL PROTECTED] wrote:
| In an attempt to patch all driver packages automatically, I've
| modified x-modular.eclass to do something along the lines of what
| elibtoolize does for its patching. However, this would require the
| storage of a patch
Joshua Baergen wrote:
In an attempt to patch all driver packages automatically, I've modified
x-modular.eclass to do something along the lines of what elibtoolize
does for its patching. However, this would require the storage of a
patch for x-modular.eclass, which I would intend to place in a
On Fri, 2005-12-09 at 12:13 -0700, Joshua Baergen wrote:
In an attempt to patch all driver packages automatically, I've modified
x-modular.eclass to do something along the lines of what elibtoolize
does for its patching. However, this would require the storage of a
patch for
Martin Schlemmer wrote:
Use ${P}-patches-{PVER}.tar.bz2, and set PVER (or whatever) before
inheriting the eclass.
Thanks, I will do that.
--
Joshua Baergen
--
gentoo-dev@gentoo.org mailing list
AREAS WE NEED HELP WITH:
1) Porting applications to modular X
2) Fixing descriptions for the vast majority of modular packages.
OK, it seems like we've now got issues resolved related to the new
virtual/x11 package. Despite all the eyes that looked at it and all the
publicity on lists and
Hello,
I am looking for help / advice to get KDE to work with htdig. I'm trying to fix
an old bug [1], but I'm not much of a KDE expert, and so far I've had no luck.
If you have any ideas and are willing to spend a few minutes helping me figure
out how to get khelpcenter and kdevelop to play nice
Mike Frysinger wrote:
so the video herd policy is to remove packages until you're left with
a small enough subset of packages you can handle ?
-mike
I'd rather say that we select packages that evolve and fit the needs and
kill what isn't suitable anymore.
There are still many way to shoot
Chandler Carruth wrote:
As a user currently, what steps could I take to help this package stay
alive? I will take them as the alternative is to put an unofficial
ebuild up on a webpage.
On my to be killed list I have
transcode 1
avifile
transcode 1 is already there and seems in good
Martin Schlemmer wrote:
Will need to do something about the default glu/opengl/xft virtuals as
well ... (you probably did not forget this, just double checking ...)
Yep.
From an email I sent in the past 24 hours:
Donnie Berkholz wrote:
Done.
I will probably do similar for the other x11
On Sat, Dec 10, 2005 at 01:09:50AM +0100, Luca Barbato wrote:
Mike Frysinger wrote:
so the video herd policy is to remove packages until you're left with
a small enough subset of packages you can handle ?
I'd rather say that we select packages that evolve and fit the needs and
kill what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Frysinger wrote:
| so the video herd policy is to remove packages until you're left with
| a small enough subset of packages you can handle ?
Quite a contrast with the x11 herd policy: to add packages until there's
10x more than you can
On Thu, Dec 08, 2005 at 09:24:57PM +0100, Marius Mauch wrote:
On Wed, 7 Dec 2005 23:49:59 +
Mike Frysinger [EMAIL PROTECTED] wrote:
this is your [belated] reminder of the December council meeting.
future reminders will not be late anymore ... we've proven that we
cant remember it so
On Friday 09 December 2005 08:19 pm, Mike Frysinger wrote:
On Sat, Dec 10, 2005 at 01:09:50AM +0100, Luca Barbato wrote:
Mike Frysinger wrote:
so the video herd policy is to remove packages until you're left with
a small enough subset of packages you can handle ?
I'd rather say that we
14 matches
Mail list logo
