1

I have a large project which contains many libraries that the main binary depends on. I would like to know what the proper way to handle this in launchpad so I can build the libraries, then the main binary and offer each debian pacakge on a ppa.

You can see the project in question at lp:snapcpp (https://code.launchpad.net/snapcpp/). In snacpp, we have "snapwebsites", a C++ CMS system which attaches to a Cassandra database via our library "libQtCassandra." "snapwebsites" depends on libQtCassandra, as it does libltd, and others. Each of these libraries need to be separate debian packages themselves. Each project has its own "debian" folder but there is no root debian folder at this time.

How can I get this to work on launchpad, which requires a root debian folder? Do I need to construct a debian project at the root that lists each dependency? If not, do I need to break up each project into its own branch using bzr? If I do the latter, how do I call out those depencency debs for the build (in other words, how do I tell the recipe for snapwebsites that it needs to have libQtCassandra and its dependency packages installed)?

Thanks!

Erbureth
  • 3,378
  • 22
  • 39
Doug Barbieri
  • 635
  • 1
  • 5
  • 16
  • 1
    Are these dependencies available in the standard main repositories? – Braiam Dec 02 '13 at 17:06
  • Braiam: no, the dependencies are part of the main project. Have a look at each subproject in the trunk: http://bazaar.launchpad.net/~doug/snapcpp/trunk/files For example, snapCMakeModules is a source-package dependency where we install custom modules into cmake's search path. All snapcpp projects depend on it. Or for another example, check out advgetopt, which allows C++-friendly command line parsing (which has a dependency on controlled_vars, also in the same project). – Doug Barbieri Dec 02 '13 at 17:50
  • Sounds like you should have each dependency in a separate project instead? – tripleee Dec 02 '13 at 18:40
  • Triplee: if I break them up into many subprojects (an issue unto itself, due bzr branches wanting to be from the root of a git project), I still run into the same issue. If I create, say, advgetopt, which depends on controlled_vars, how do I tell the launchpad.net build system that it requires controlled_vars to be built and installed first? – Doug Barbieri Dec 02 '13 at 18:52

1 Answers1

1

The solution that I discovered on my own was to utilize the recipe command "nest-part," which allows you to take a single folder out of a bzr branch and map it into your project. It cannot, however, map to the root of your branch.

What I did was to create a branch with only packaging information in it, and a CMakeLists.txt file containing "add_subdirectory(src)". Then I map from the main code branch (lp:snapcpp), but only the project in question. For example, here is the recipe for the "controlled_vars" project in snapcpp:

# bzr-builder format 0.3 deb-version {debupstream}+{revno}
lp:~snapcpp/snapcpp/controlled_vars
nest-part src lp:snapcpp controlled_vars src

There does need to be a branch with packaging information with each sub-project, but this is a one-time set up issue.

Doug Barbieri
  • 635
  • 1
  • 5
  • 16