On Sat, 2013-02-02 at 17:58 +0100, Pierre-Yves Chibon wrote:
On Fri, Jan 11, 2013 at 01:53:49PM -0500, Seth Vidal wrote:
> coprcli create mycopr -r epel-5 -r epel-6 -r fedora-18 -a i386 -a x86_64
Ok so this is implemented API side and CLI side.
> coprcli build mycopr pkg1 pkg2 pkg3
I just sent patches for this on the API side, I still have to do the CLI part
but it should be pretty straight forward.
> coprcli info mycopr | python -m json.tool | check for something_or_another
What's the idea behind this one?
Returning raw json? Or just giving information about a copr (owner, chroots,
packages (?), builds (I have no real idea of what we can/display))?
Seth?
BTW, I wanted to look at cliff because pkwat uses it and it seems pretty
cool. Now that I have seen it, I have the feeling that it does not quite
fit our use-case and it nicely adds a dependency and a layer of
complexity when developing the application.
If I rewrite the cli to a more common argparse based CLI, anything
against?
Pierre