Added setup.py

[petevg]

Makes it possible to add plugins as a depedency to another project (for
example, gh:juju-solutions/matrix, which is what prompted this
change).

The setup.py puts all the scripts in Python's bin dir, naturally adding
them to the path in your current Python environment.

@johnsca

[johnsca]

+1 this makes it easier to manage the path, though I'd also like to see this grow a snap.yaml as well.

[marcoceppi]

Why are people depending on plugins? It's not a viable long term decision. Plugins are temporary play grounds for piloting features in juju.

…

On Tue, Jan 31, 2017 at 6:08 AM Cory Johns ***@***.***> wrote: +1 this makes it easier to manage the path, though I'd also like to see this grow a snap.yaml as well. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#75 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAET1aXlQP26_i3AWGKI1keWU56lgfyUks5rXmmsgaJpZM4LTZnb> .

[petevg]

@marcoceppi the cwr-ci bundle wants to run juju-crashdump in order to gather logs from a test run. @johnsca also wants to drop it into bundletester. It's a useful bit of functionality.

I can drop the code from the juju-crashdump script into both matrix and bundletester, but the script is kind of inherently tricky, and I'd rather not be maintaining a tricky, oft patched script in two different places. :-/

[marcoceppi]

The general guideance has been, if it requires a set of deps or more complexity than a one off script, it should be it's own project. This is what juju-wait and others have done, I'd recommend this route for this plugin.

Think of the plugins repo as an incubation project, it sounds like this plugin has just graduated.

[petevg]

@marcoceppi That sounds sensible. I will move it into its own space.