| 1 |
On Tue, 28 Aug 2012 09:43:37 +0200 |
| 2 |
hasufell <hasufell@g.o> wrote: |
| 3 |
|
| 4 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 5 |
> Hash: SHA1 |
| 6 |
> |
| 7 |
> On 08/28/2012 06:26 AM, Arfrever Frehtes Taifersar Arahesis wrote: |
| 8 |
> > |
| 9 |
> > There needs to be a way to specify maximal accepted slot of Boost. |
| 10 |
> > Examples of some possibilities: * BOOST_MAX_SLOT="1.49" global |
| 11 |
> > variable * '--max 1.49' arguments for boost-utils_get_* functions |
| 12 |
> > |
| 13 |
> |
| 14 |
> Exactly. I don't see any reason for this eclass except this feature. |
| 15 |
> The current expected behavior of boost and build systems is that |
| 16 |
> always the latest installed will be picked. |
| 17 |
> |
| 18 |
> In fact this breaks packages in 3 of 4 cases on new boost versions. |
| 19 |
> |
| 20 |
> And while we are it it, we can punt the useless eselect |
| 21 |
|
| 22 |
It was queued for punting. That's reason for the eclass. |
| 23 |
|
| 24 |
-- |
| 25 |
Best regards, |
| 26 |
Michał Górny |
Archives