| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 08/28/2012 06:26 AM, Arfrever Frehtes Taifersar Arahesis wrote: |
| 5 |
> |
| 6 |
> There needs to be a way to specify maximal accepted slot of Boost. |
| 7 |
> Examples of some possibilities: * BOOST_MAX_SLOT="1.49" global |
| 8 |
> variable * '--max 1.49' arguments for boost-utils_get_* functions |
| 9 |
> |
| 10 |
|
| 11 |
Exactly. I don't see any reason for this eclass except this feature. |
| 12 |
The current expected behavior of boost and build systems is that |
| 13 |
always the latest installed will be picked. |
| 14 |
|
| 15 |
In fact this breaks packages in 3 of 4 cases on new boost versions. |
| 16 |
|
| 17 |
And while we are it it, we can punt the useless eselect implementation. |
| 18 |
-----BEGIN PGP SIGNATURE----- |
| 19 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 20 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 21 |
|
| 22 |
iQEcBAEBAgAGBQJQPHapAAoJEFpvPKfnPDWzAz8H/0/57b9AiYMxPM9APK5nSLCl |
| 23 |
UGuaeh+Jnz8kTIzaVE0BNP2QSNkMZqVMa9hWnHgZHG+9Ne1zgCPU2PP8hijnwWb3 |
| 24 |
JWI02t/iWfsMqY8KNMNlCbyL21r5FurIXS66KHB90bygnaZZxgGZZJ6GUNEqKH5F |
| 25 |
qPZUA++4NXnRbAU2dotaJH77v6fUXuzB/fhcrz9YmlDss+VGgxGSEGx2YJDU7WKu |
| 26 |
4U4kawNRFxc5eJaj4ciOOeGMk4mnwq6459p9F/Kjzx3XniNCuKEA0G81Fn2GmOxe |
| 27 |
fLurBlzj2gwsg8dy+TL9VwLDwESELLZ645u3Y0SEqp34Zo+OAFdytmYg6uxP8l0= |
| 28 |
=o3qr |
| 29 |
-----END PGP SIGNATURE----- |
Archives