Merge lp:~jml/pkgme/include-backends into lp:pkgme

[Jonathan Lange]

This branch changes the default way that pkgme looks for backends. Instead of just looking inside a pre-defined system-wide path, pkgme looks for a setuptools entry point called 'get_backends_path'. It also uses pkg_resources to make sure that any backends bundled with pkgme are included. Any setuptools packages that have this entry point can return a path that is appended to the backend search path.

The motivation is to be able to use pkgme as a dependency in egg-driven deployments, such as those in lp:pkgme-service.

 * I haven't updated the docs. Should I?
 * This probably deserves a release and a version number bump
 * Not sure about the order of bundled packages vs system installed packages

Also, I had to add launchpadlib as a dependency.

jml

[James Westby (james-w)]

Hi,

This looks pretty good, it's a small change. I've no real idea how to test
it.

I don't know what order the paths should be in, but I think this order is
as good as any.

Updating the docs is a good idea, as backend authors will need to know about
the options.

Thanks,

James

review: Approve

[lp:~jml/pkgme/include-backends]

92. By Jonathan Lange on 2011-11-16

Extended documentation on how pkgme finds backends.