Requesting ebuild for txJSON-RPC - json rpc library for twisted Reproducible: Always
Got ebuild at https://github.com/yaccz/yacs-gentoo-overlay/blob/master/dev-python/txJSON-RPC/txJSON-RPC-0.3.1.ebuild but I'm not sure wheter to choose name txJSON-RPC or txjsonrpc (which is how the python package is called). In the gx86 I'd go with the txjsonrpc, what do you think?
Also I found discrepancy in the license declaration by setup.py and the actual LICENSE file included, reported at https://bugs.launchpad.net/txjsonrpc/+bug/1264085 The ebuild probably shouldn't go into gx86 until this is resolved?
What is/will it be used by? I recall we had a policy on not adding packages that are not directly deps of some software.
I need it for my proprietary app. What kind of policy is that? Where is it defined? Who created it?
I don't think there's a policy, but I have said in the past that one single user requesting some ebuild shouldn't always be good enough to have the python team maintaining something forever. Since you're a developer, that's slightly different, since you can take care of maintenance yourself. Still, if there's only a limited amount of usage/rdeps, it might be nice if you also make yourself an explicit maintainer, instead of just leaving things to python. I hope that makes sense. Maybe we should have a discussion somewhere about making it into an actual policy? I don't think it's always very clear-cut...
Oh well, I can keep it in my overlay (yac) or maybe sunrise? and if there is another request I can push to gx86.
I'm really fine with you putting it in gentoo-x86! I only care about making sure we don't stretch the python team too thinly, having them do maintenance for packages that really don't get used too much.
