I had a problem with the portdir_overlay option in the snapshot section.
What it appears to be doing today is merely copying in the contents of
the overlay directory on top of the existing Portage directory
structure. I'm certainly no Portage expert, but I don't think that's
how the $PORTDIR_OVERLAY setting in Portage works, is it? I think if
Portage finds a directory in $PORTDIR_OVERLAY it takes those contents
and ignores any contents from the "normal" /usr/portage... doesn't it?
The problem I had was I wanted an updated version of dev-python/quixote
so I created my own overlay directory dev-python/quixote, then I created
an ebuild in there, ran ebuild ... digest, and called it good. I didn't
have a ChangeLog or metadata.xml in my version, nor did I have the
previously existing ebuilds in my version.
But, when I tried to use the portage_overlay ability of Catalyst, it
broke because it copied my files into the portage directory without
deleting the previous contents. Portage got upset because it found
files there which weren't listed in the Manifest, and refused to merge
the package.
I fixed this by copying all the original files into my overlay, but it
seems to me that Catalyst should not just copy the overlay files: it
should remove the existing directory (e.g.,
...usr/portage/dev-python/quixote) first, then copy in the overlay
version.
Thoughts on this?
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith-ZIRUuHA3oDzQT0dZR+AlfA@xxxxxxxxxxxxxxxx>
HASMAT: HA Software Mthds & Tools
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
gentoo-catalyst-aBrp7R+bbdUdnm+yROfE0A@xxxxxxxxxxxxxxxx mailing list
|
