Michał Górny posted on Sun, 20 Aug 2017 12:26:48 +0200 as excerpted: > --- /dev/null > +++ b/dev-util/shadowman/shadowman-9999.ebuild > @@ -0,0 +1,27 @@ [snip...] > +# note: only for testing > +KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 > ~s390 ~sh ~sparc ~x86"
OK, I know you said this was only for testing, but a question I had the first time around and didn't ask... It seems to me just as easy... and less chance of potential problems should a tester accidentally commit it, to handle it the way gentoo/kde does with live and not-yet-ready ebuilds in their overlay: Blank keywords in the ebuild and add it to package.accept_keywords (or simply package.keywords if you prefer the old name) with a ** entry if you're testing. Example from my package.accept_keywords (this entry might be in the symlinkable files in the overlay now, but it wasn't when I created it): # 2017.0611 kirigami needed for kde systemsettings # might as well do it live-9999 too =kde-frameworks/kirigami-9999 ** Not that it matters particularly, but is there a reason you chose to put the keywords in the ebuild instead of having people do the ** thing as above? A blank keywords, thereby forcing people who actually want to test to do the ** thing, would seem less of an invitation to problems should someone accidentally commit it during testing (tho admittedly this is a new package so problems are less likely, but I'm just used to seeing it require the ** accept_keyword thing). So I'm just wondering what reason you might have had to do it this way instead. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman