On Friday 29 July 2005 17:58, Duncan wrote: > Diego 'Flameeyes' Pettenò posted > <[EMAIL PROTECTED]>, excerpted below, > > on Fri, 29 Jul 2005 16:11:46 +0200: > > On Friday 29 July 2005 16:05, Dan Armak wrote: > >> Anyway, the effective change would be to die if patching fails (and > >> support patchlevels != 0), so my orig question stands. > > > > epatch already takes care of failing, that's why I was thinking about > > that > > > > :) > > More on the point... what about replacing the current base.eclass code > with appropriate calls to epatch? This would mean changes/fixes to epatch > would automatically propagate, while continuing to maintain compatibility > by keeping the base.eclass functionality around. Well as I wrote in my previous reply, I see no objection. I wanted to make sure this is OK with all base.eclass users, beyond kde.eclass.
-- 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
Description: PGP signature