Jauhien Piatlicki wrote: > The question is not about crap in the upstream, but about changed > dependencies, behavior, whatever else.
That's a good point. > E.g. we in downstream have some patches, when upstream changes > related code (e.g. applying our patches), ebuild fails to build. I consider this a separate issue however. I would actually expect there to be a policy which forbids patches on live ebuilds. Make another live ebuild or maybe an overlay if you want to offer a different set of commits than the upstream repo. For me, the whole point of live ebuilds is that they are the latest upstream code, no more, no less. > Everything in live ebuild can change, so it will fail. > It can be not crap, but some improvements, but it does not matter > for the possibility of building of a given ebuild. Patches aside I completely agree that a live ebuild is a moving target, but to me that is a good thing, in fact the very essence of open source. //Peter
pgpyQvgFUWt1q.pgp
Description: PGP signature
