On Friday 18 February 2005 14:47, Jason Stubbs wrote: > Correction: The eclass caching mechanism looks at the repository that the > ebuild was defined in. Therefore, the only people that are at risk are > those that use their CVS repository as PORTDIR or in PORTDIR_OVERLAY. > > So, here's the deal... Umm, I was going to write what the deal is, but I'm > still trying to figure it out. :( This isn't news, at least to me and some other devs... I last ran into this when I was managing the split ebuilds overlay in subversion @ berlios, and began importing the ebuilds into portage cvs.
The deal is that you should never ever have non-identical copies of the same eclass in more than one place (whether PORTDIR or overlay). > > Anyway, the thing I/we (I'll be gone for the weekend) need to know right > now is what people are willing to sacrifice and what they are not in order > to get a speedy (even if only temporary) resolution. What do you mean by 'sacrifice'? It's already broken and, AFAIK, has always been that way. Any change would have to be an improvement, wouldn't it? -- Dan Armak Gentoo Linux developer (KDE) Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD 0069 508D 9143 8D5F 8951
pgpVvcVI1fT3B.pgp
Description: PGP signature
