On 02/14/2011 07:52 PM, "Paweł Hajdan, Jr." wrote: > On 2/14/11 3:07 PM, Tomáš Chvátal wrote: >> Same does x11 team... >> Example: >> http://bugs.gentoo.org/show_bug.cgi?id=354237 >> >> I think this does not need any policy, most teams can use brains and >> fill the bugs quite conveniently :) > > Well, that's the entire point. For the bug you cited, and - for another > example - http://bugs.gentoo.org/show_bug.cgi?id=353434 I can't just > copy-paste something to my package.keywords file. > > The table is indeed pretty, and it has value, but I'm just asking for a > bit more convenience. > > One more time, the good examples are: > > http://bugs.gentoo.org/show_bug.cgi?id=322791 > http://bugs.gentoo.org/show_bug.cgi?id=329703 > > Citing part of good example inline: > >> Stabilization list for x86: >> =========================== >> >> =media-libs/gstreamer-0.10.29 >> >> =media-libs/gst-plugins-base-0.10.29 >> =media-plugins/gst-plugins-alsa-0.10.29 >> =media-plugins/gst-plugins-cdparanoia-0.10.29 > > And citing part of *bad* example inline: > >> app-admin/eselect-opengl-1.2.1 alpha amd64 arm ppc ppc64 s390 x86 >> media-libs/mesa-7.9.1 alpha amd64 arm ppc ppc64 x86 > > The *good* example can be copy-pasted to package.keywords with no > editing. The *bad* examples requires some editing, and while it can be > automated, there are different formatting conventions, etc etc so IMHO > it's not really feasible. >
And http://bugs.gentoo.org/show_bug.cgi?id=349053#c1 ? I tried to provide a clue howto get usable p.keywords list easy. - Samuli
