Moving pwclient into its own project

Jeremy Kerr jk at
Sat Mar 25 00:36:14 AEDT 2017

Hi Stephen,

> I'd like to move pwclient into its own project/repo/possibly mailing
> list. There are a couple of reasons for doing this:

I have no specific objections to this (aside from splitting the mailing
list - I think it'd be a mistake to split the potential community
there), but:

> - I want to be able to package this up for PyPi to allow installation
>   with pip

Makes sense; I have very little experience with PyPi, but does that mean
we need separate repos?

> - I want to be able to release new pwclient features to everyone
>   without waiting for their patchwork admin to bump the Patchwork
>   version

I don't see why that needs an update? There should be separate channels
for each of these.

> - I want to be able to provide more comprehensive documentation for
>   pwclient, as it slowly morphs into a VCS-independent, general-purpose
>   Patchwork CLI tool

That sounds awesome, but doesn't mean we need a separate repo.

> - (stretch goal) I'd like to create deb/rpm packages for Fedora,
>   Ubuntu, etc.

Distros should have no issue with producing multiple (installable)
binary packages from one source package.

Overall, I'm not convinced that this is a good idea, but I'm certainly
not the deciding factor in this :)



More information about the Patchwork mailing list