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

[Leandro Lucarella]

I just did a search on closed bugs for this problem and I realized this is
a *very* recurrent bug. Even when the Debian policy might accept the
current dependency scheme, I think it would be best to rethink how boost
is packaged to avoid this issues. Unfortunately the packages separation
Debian choose is not very close on how Boost is developed and this
artificial separation is starting to show and being a little annoying (for
users and for maintainers, as the bogus bug reports keep coming).

I know Boost probably should be better organized in upstream to allow
efficient packaging, but that's not how things are, and going against that
could be very time consuming and frustrating.

I hope you can consider another way to make packages from boost that don't
imply making the user handle the dependencies himself.


Thanks.

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
A can of diet coke will float in water
While a can of regular coke will sink