Debian et al ship the stuff in test/ under a package called "bluez-utils", adding the prefix "bluez-" to the executables. It seems to be all python 2.x stuff (no python 3 support) but there are some really useful things in here. They could be added as USE=utils or USE=examples perhaps? utils seems to be what debian et all call them. I would be willing to do the work if you nod, or you can do it, either way.
Feel free to go ahead and add that USE "utils" :) Anyway, please don't enable it by default as upstream thinks most of that stuff is not for "standard" users and that utils could have unfixed bugs and so ;)
entirely agreed, thanks, I'll work on it.
I have added an -r1 ebuild and used the pre-existing "test-programs" use flag since we already had it for the same thing. I've implemented it slightly differently to make it a bit more usable (especially since the old version didn't install test-discovery which is what I care about most) The python team gave me some pointers to clean up and I handled as much as I could but until they have given a full review and signed off I've pulled the keywords from my ebuild. It works, but I got some flak for running python_fix_shebang and symlinking stuff into /usr/bin so I'll wait for a little help to fix that before re-adding the keywords.
the deed is done. I left it in ~arch for now despite almost nothing effectively changing. we can stabilize it in a little while after 5.35 is fully stable if we want.
Do you need it stable so fast? In general, upstream tends to make a new release every month, then, maybe we could wait for the next major version :/ Thanks for the work :)
(In reply to Pacho Ramos from comment #5) > Do you need it stable so fast? In general, upstream tends to make a new > release every month, then, maybe we could wait for the next major version :/ > > Thanks for the work :) as I said in my comment (and my commit message fixing the accidental stable on amd64) I have no need to rush this to stabilization. especially since I just added a -r2 with a new executable from the tools dir (as suggested by the upstream author) I suspect stabilizing this work with the next release is fine.
