Re: [Boost-bugs] [Boost C++ Libraries] #12033: Boostdep misses some dependent components

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #12033: Boostdep misses some dependent components
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2016-03-01 17:03:45

#12033: Boostdep misses some dependent components
-------------------------------+----------------------------
  Reporter:  edaskel@…         |      Owner:  pdimov
      Type:  Bugs              |     Status:  assigned
 Milestone:  To Be Determined  |  Component:  Building Boost
   Version:  Boost 1.61.0      |   Severity:  Problem
Resolution:                    |   Keywords:  boostdep
-------------------------------+----------------------------

Comment (by pdimov):

 > Thanks for the information.  It seems that "secondary" lists some
 dependencies that are not necessary for me - for example, container,
 iterator, range and python.  Perhaps one of the primary dependencies
 requires them for a header I don't use.

 That's how `boostdep` works, yes. It tracks dependencies on a coarse
 module level, and not on a header file level. If you want to just extract
 the minimal subset required for `msm`, you can use `bcp`, which does work
 on a header level.

 When you tell `bpm` to install `msm`, and it installs a dependent module
 `M` which uses, say, `iterator`, it also installs `iterator` because
 otherwise you'd have a working `msm` but won't have a working `M`, and
 `bpm` doesn't do such partial installs.

 We've done some work to reduce unnecessary dependencies and make subsets
 leaner, but there remains a lot to be done, and many maintainers don't
 consider it a priority as Boost is still oriented towards monolithic
 releases. Sorry. :-)

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/12033#comment:5>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.