[pkg-boost-devel] Bug#553281: Bug#553281: Related bugs

[Leandro Lucarella]

troy d. straszheim, el  2 de noviembre a las 21:57 me escribiste:
> But there is an argument to be made that until boost itself knows
> what modularity means, one should just package boost-libs and
> boost-headers and be done with it.   Boost is a monolith.  It
> doesn't mean you've done poorly if you package it that way.

I think as long as Boost is monolith, maybe it would be best to pack it
that way. I think the current situation is the worst, because the user
easily find himself doing manual dependency (and reporting bogus bugs
until he realizes how things works :).

I think libboost-dev (*all* the headers) + libboost-xxx (one package per
library) packages can be enough.

Another option is to split Boost into real small parts, like in the
dependency graph you linked, but this would be a nightmare to maintain
because of the excessive dependencies, I think, so it might not worth it,
and again, it goes against how Boost is designed (as a monolith library).

> I mentioned that there are fedora and exherbo guys involved in the
> boost-cmake effort.   Also there are several core cmake devs from
> kitware.  As a longtime debian user I'd be more than happy to help
> my favorite distro maintain my favorite c++ library.   More info on
> boost-cmake is available here:
> 
>   https://svn.boost.org/trac/boost/wiki/CMake
> 
> I'm on all those lists and IRC channels.  So..  if this is at all
> interesting, please get in touch.

I'm glad you are trying to fix this from the root. I don't really see as
a big problem boost being monolith, I'm just worried about Debian broken
dependencies. It would be nice if it were modular though, so I appreciate
the effort, but I'm not that interested on working on it. I'm sorry, and
thanks again.

-- 
Leandro Lucarella
Integratech S.A.
4571-5252