Re: [Boost-cmake] auto-modularization. Time to merge to main release branch?

From: Doug Gregor (doug.gregor_at_[hidden])
Date: 2008-07-03 10:58:30

On Thu, Jul 3, 2008 at 10:24 AM, troy d. straszheim <troy_at_[hidden]> wrote:
> Beman Dawes wrote:
> Ok.  As it turns out, now that our directory hierarchy again mirrors that of
> branches/release, it isn't so bad to just track the release branch.  I'm
> content to wait on merging with trunk, we don't have the manpower to
> maintain two branches and are focused on branches/release
> in order to get installers built as close to the main 1.36.0 release as
> possible.

Right. At this point, being in trunk would actually be more work than
where we are now, so let's wait.

> Do we know who does packaging for the major linux distributions?  It would
> be good to look at making .debs and .rpms as well.

For now, I suggest that we let those packagers do their thing, and
focus on Windows+Mac installers and regression testing. Someone in the
CMake community is working on extending the CPack components system to
create families of Debian packages from the components. When he gets
that working, it will become very, very easy to us to build a set of
.debs (with dependencies and so on) for Boost. Given that someone else
is going to be doing most of this work anyway, let's wait and see what
happens.

If we really want to help packagers, we should be adding support for
creating pkgconfig files from CMakeLists.txt as part of the build
process. Then Boost can be used more easily from autotools-based and
one-off projects.

  - Doug