Other than a text editor?
I'd like to have a tool that can add USE flags on a per package or
global level. (I'm doing this in some build scripts and would prefer
just to have a tool, rather than sed or some other shell hackery).
I couldn't find anything via a quick search on google.
Here's my
On 5/9/06, Duncan [EMAIL PROTECTED] wrote:
m h posted [EMAIL PROTECTED],
excerpted below, on Mon, 08 May 2006 21:38:49 -0700:
hat is the status of my patches? I'm assumming that they are
rejected... I'm curious the know the reason. If the plan is to
migrate to a new improved version
is going to be around for a while, why
the objection to cleaning up the code?
Not meaning to fan any flames here. I'm not on IRC 24-7, so I
probably miss a lot of the action.
thanks
matt
On 5/2/06, m h [EMAIL PROTECTED] wrote:
Here's a stab at pre10...
The order of application is the order
feedback is welcome.
-matt
On 5/1/06, m h [EMAIL PROTECTED] wrote:
Based on the recent Stabilizing portage 2.1 thread, should I provide
patches based on pre9 or pre10?
thanks
matt
On 4/30/06, Donnie Berkholz [EMAIL PROTECTED] wrote:
m h wrote:
OK will do that. Since, I'm not a patching pro
Based on the recent Stabilizing portage 2.1 thread, should I provide
patches based on pre9 or pre10?
thanks
matt
On 4/30/06, Donnie Berkholz [EMAIL PROTECTED] wrote:
m h wrote:
OK will do that. Since, I'm not a patching pro, can you suggest a
good way of creating a series of patches
with the revamp of Global vars in one commit, and
then the re-arrangement in the other.
m h wrote:
Yes, I can break it up, but it will probably be 3 one line changes and
one big 1000 line change. The 1000 line change is pretty
straightforward. The only real code changes per se are removing any
Upon further testing, I'm updating a line in the patch
On 4/28/06, m h [EMAIL PROTECTED] wrote:
Folks-
I'm submitting a patch of a refactoring of the emerge code in
2.1_pre9-r5. This patch adds no features per se. But I believe it
makes the code much more readable. This only addresses
to
figure out what/when/where happened
m h wrote:
Upon further testing, I'm updating a line in the patch
On 4/28/06, m h [EMAIL PROTECTED] wrote:
Folks-
I'm submitting a patch of a refactoring of the emerge code in
2.1_pre9-r5. This patch adds no features per se. But I believe it
makes
Hmmm, then I must be missing where the spec file gets generated,
because there is no code in ebuild.py that does it...
On 10/26/05, Zac Medico [EMAIL PROTECTED] wrote:
m h wrote:
I'm trying to run
ebuild path/to/ebuild rpm
and it's failing because there is no .spec file from which to build
/). If anyone can
elaborate on the efforts going on in that arena, I'm all ears.
matt
On 10/5/05, Alec Joseph Warner [EMAIL PROTECTED] wrote:
m h wrote:
Hey Folks-
I'm working on trying to get prefixed installs working. (As such, I'm
using some code kindly modified by Michael Haubenwallner
On 10/5/05, Brian Harring [EMAIL PROTECTED] wrote:
On Wed, Oct 05, 2005 at 01:48:03PM -0700, m h wrote:
On 10/5/05, Brian Harring [EMAIL PROTECTED] wrote:
Yay, time for another flame war (just what I'd love to spend my time
on).
Sorry, I'm really not trying to kindle any flames here
Thanks for the warning Alec. Since I already have very limited
knowledge of the internals, I figure this will be a good trial by fire
(learn sort of the portage internals and issues with prefixed
installs). If it works, perhaps I will be able to devote more time to
it and do more than a simple
Michael-
Thanks for your reply.
Is it possible to put your complete steps along with links to custom code you've done in the gentoo wiki?
I'd very much like to try and replicate what you have done.
thanks againOn 9/9/05, Michael Haubenwallner [EMAIL PROTECTED] wrote:
Hi Matt,m h wrote: Hi
13 matches
Mail list logo
