Add a convenience shell script to install deps

hrm... I guess the standard Python way of doing this (having setup install things) is in direct conflict with the Ubuntu way (system packages). I'll add a utility function, and see how that works.

So, apparently the setup.py script is now a little bit broken. What's more:

 * setup.py won't be used to install dependencies;
 * ultimately, this will be packaged in Ubuntu (or a PPA) and the dependencies will be configured in the .deb file
 * for now, it would be useful to have a script that could install the deps for developers

To that last point, I will re-target this bug, changing the summary from "Missing dependencies in setup.py" to something more reasonable, given this info.

So the way I understand this works is that setup.py allows you to provide some information about the project and when you run 'quickly package' it detects the imports and identifies which package dependencies it has. Again, I think we should see if a Quickly dev can weigh in here to see if Quickly can do this for us.

On Mon, Mar 5, 2012 at 1:03 AM, Jono Bacon <email address hidden> wrote:
> So the way I understand this works is that setup.py allows you to
> provide some information about the project and when you run 'quickly
> package' it detects the imports and identifies which package
> dependencies it has.

So... the Python packages up on PyPI usually have different names than
the Ubuntu packages. If quickly does support using the "requires"
option to install packages via apt-get, we'll definitely need someone
to clarify the mechanism there ;-) (as you said below).

> Again, I think we should see if a Quickly dev can
> weigh in here to see if Quickly can do this for us.

Previously when I have created Quicky projects the dep checker has known how to map import modules to the correct packages. I mailed Michael Terry to see if he can weigh in on this.

On Mon, Mar 5, 2012 at 2:14 PM, Jono Bacon <email address hidden> wrote:
> Previously when I have created Quicky projects the dep checker has known
> how to map import modules to the correct packages.

/me nods

> I mailed Michael
> Terry to see if he can weigh in on this.

Sweet!

d

Is this bug still valid since we have a real package now?

When writing code for a project, devs often don't have the package in question installed on their systems (so as to prevent source ambiguity). As such, I would imagine that this is still useful.

If there was a *meta* package that just set up deps and other magic, but without actually installing the daemon, library, etc., then there would be no need for the script; the instructions on the wiki for getting a dev env set up easily would include the apt-get install command for the meta package.

Or, alternatively, if Quickly has this capability and the deps can be installed via a Quickly subcommand...

I think I am going to mark this as Won't Fix as people can determine the deps either from build-deps or from the build documentation.