| 1 |
Hello, |
| 2 |
|
| 3 |
a user submitted a bug[1] that cmake always select the latest boost. We the |
| 4 |
kde team as cmake maintainer found a solution to respect the (e)selected |
| 5 |
boost. The patched version is not in tree yet, because after my blog post[2] |
| 6 |
about this issue a discussion in the bug starts. |
| 7 |
|
| 8 |
Summary of the comments: |
| 9 |
1) Ebuilds should always pick the latest boost version. |
| 10 |
2) Boost should be compared to gcc, python, ruby etc |
| 11 |
|
| 12 |
So please state your opinion here, before the bug comments explode. In the |
| 13 |
case that eselect feature for boost will be last rited as in comment 16[1] |
| 14 |
announced, then you can forget this mail. |
| 15 |
|
| 16 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=335108 |
| 17 |
[2] http://blogs.gentoo.org/johu/2012/01/13/cmake-picks-always-the-latest- |
| 18 |
boost/ |
| 19 |
|
| 20 |
Greetings |
| 21 |
-- |
| 22 |
Johannes Huber (johu) |
| 23 |
Gentoo Linux Developer / KDE Team |
| 24 |
GPG Key ID F3CFD2BD |
Archives