Michał Górny: > > And how can you test a VCS ebuild? You can't assume upstream will be > stuck on one commit. >
I don't see the argument. It sounds like you are saying "one day, upstream might stop supporting architecture xy, so better we just omit all of them from KEYWORDS". Err? For example, I know polarssl upstream will support amd64 and x86 for the foreseeable future (cause they told me and I run the live ebuild on both arches). Why would I want empty KEYWORDS, even in the live ebuild? Bugs will be valid and fixed. If an architecture is no longer supported and upstream doesn't accept bugs for it any more, drop it. Same as always.
