Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bugzilla DB migration completed. Please report issues to Infra team via email via infra@gentoo.org or IRC
Bug 495976 - dev-python/txJSON-RPC dev-python/txjsonrpc - JSON RPC library for dev-python/twisted
Summary: dev-python/txJSON-RPC dev-python/txjsonrpc - JSON RPC library for dev-python/...
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Default Assignee for New Packages
URL: https://pypi.org/project/txJSON-RPC/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-25 11:13 UTC by Jan Matějka (RETIRED)
Modified: 2019-05-18 09:40 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Matějka (RETIRED) gentoo-dev 2013-12-25 11:13:00 UTC
Requesting ebuild for txJSON-RPC - json rpc library for twisted

Reproducible: Always
Comment 1 Jan Matějka (RETIRED) gentoo-dev 2013-12-25 11:56:50 UTC
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?
Comment 2 Jan Matějka (RETIRED) gentoo-dev 2013-12-25 11:59:20 UTC
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?
Comment 3 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2013-12-27 08:29:28 UTC
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.
Comment 4 Jan Matějka (RETIRED) gentoo-dev 2013-12-27 10:42:06 UTC
I need it for my proprietary app.

What kind of policy is that? Where is it defined? Who created it?
Comment 5 Dirkjan Ochtman gentoo-dev 2013-12-27 12:32:19 UTC
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...
Comment 6 Jan Matějka (RETIRED) gentoo-dev 2013-12-27 12:48:55 UTC
Oh well, I can keep it in my overlay (yac) or maybe sunrise? and if there is another request I can push to gx86.
Comment 7 Dirkjan Ochtman gentoo-dev 2013-12-27 12:54:06 UTC
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.