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