Am Dienstag, den 28.08.2012, 09:43 +0200 schrieb hasufell: > On 08/28/2012 06:26 AM, Arfrever Frehtes Taifersar Arahesis wrote: > > > > There needs to be a way to specify maximal accepted slot of Boost. > > Examples of some possibilities: * BOOST_MAX_SLOT="1.49" global > > variable * '--max 1.49' arguments for boost-utils_get_* functions > > > > Exactly. I don't see any reason for this eclass except this feature. > The current expected behavior of boost and build systems is that > always the latest installed will be picked. > > In fact this breaks packages in 3 of 4 cases on new boost versions. > > And while we are it it, we can punt the useless eselect implementation.
boost-1.50 already removes symlinks created by eselect-boost and doesn't depend on it anymore.
