On 03/21/2017 11:00 AM, Alexis Ballier wrote: > On Tue, 21 Mar 2017 10:41:58 +0100 > Kristian Fiskerstrand <k...@gentoo.org> wrote: >
> yes, that's the naming i suggested in the part you cut :) Indeed > > but then you'd need boilerplate duplicated code to ensure nothing but > the dedicated package can use that, and still, this doesn't rule out Or just a policy, technical solutions isn't needed for everything, and it'd make it explicit that should not be depended on by others so can't complain about breakages etc. > overlays: you can atomically change cat/pkg/*.ebuild, cat-pkg.eclass, > but then an overlay with cat/pkg and ::gentoo as master will break if > it didn't copy cat-pkg.eclass. > > with eblits in e.g. $FILESDIR, $FILESDIR points to the overlay's > location so it is clear that changing it in ::gentoo wont affect the > overlay. > (that's probably something to add to the 'pros' section too actually) > Interesting.. > I'm one of those that believe "if you exposed an API, then it becomes > public and you have to maintain that properly; no matter if there are > obvious consumers or not, since the possibility exists you have to > account for that", which is what happens with every eclass wrt overlays. > Depends on the stated policies, but in general I agree it is a good approach to plan like it is (and quite useful to ensure planning a bit instead of just rolling something out). -- Kristian Fiskerstrand OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
