Ok,
Well, what if instead we were to try and treat the overlay trees as
exactly that, overlays. So the moves were used from the lowest layer
(ie the main tree) unless a higher up layer overrode them, could that
work? It would mean effectively that the overlay moves were global, but
I guess
On Mon, 9 Jan 2006 10:21:49 -0500
Alec Warner [EMAIL PROTECTED] wrote:
My Apologies, KMail died, and when I restarted it it had the mail but
stripped the attachment ;)
-- Forwarded Message --
Subject: /etc/portage/profile/{pmask,arch.list, categories}
Date: Monday 09
Is there any feedback on my recent post?
The collision-protect feature didn't recognize two files as the same, if they
were symlinked.
i.e. /usr/FILE and /usr/X11R6/FILE caused a collision, while X11R6 - . linked
This patch for portage-2.1 should fix this. Works fine for me in all thinkable
Currently vardbapi.aux_get only works for a subset of all auxdbkeys, as
some like KEYWORDS or DESCRIPTIOn aren't stored in vdb directly.
They are however stored in environment.bz2, but not accessible
there.
This is unintuitive and limits tools like equery or my own auxget
and metascan tools in
Hi,
Since a long time I wanted to start a project like emaint ... now there it
is :-).
Currently we have two kinds of config files for portage:
o user editable (like /etc/portage/package.*)
o not user editable (like /var/lib/portage/world, as it is rewritten all of
the time and no comments
