Launchpad itself

How to handle project dependencies?

Asked by mizipzor

Say I want to create a project, A, that uses 3rd party api's/frameworks B and C. Upon checkout/branch, all three projects should be downloaded and ready to be compiled and executed.

Whats the best way to handle this? Register branch A and upload the source from project B and C to that repository? Seems like a waste of space, and I would have to handle updates to B and C manually.

In short, Im looking for something like svn:externals.

Another way is to have just our own code in branch A, which doesnt compile on its own, but in the project description we state "download this and that and place it there and there, then compile".

Maybe a "superproject" that holds both A, B and C.

Any thoughts?

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Francis J. Lacoste (flacoste) said : 		#1

It really depends on the build system you are using.

If your project is python based, you should look into zc.buildout which allows maintaining such dependencies.
http://pypi.python.org/pypi/zc.buildout

The bottom line though is that maintaining these dependencies is a build-system level features and Launchpad cannot really help in that area.

Can you help with this problem?

Provide an answer of your own, or ask mizipzor for more information if necessary.

To post a message you must log in.