Am Donnerstag, den 19.01.2012, 11:50 -0500 schrieb Ian Stakenvicius:
> On 19/01/12 03:27 AM, "Paweł Hajdan, Jr." wrote:
> > On 1/19/12 9:05 AM, Johannes Huber wrote:
> >> Summary of the comments: 1) Ebuilds should always pick the latest
> >> boost version. 2) Boost should be compared to gcc, python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 19 Jan 2012 11:50:47 -0500
Ian Stakenvicius wrote:
> I thought there was a push to eventually de-slot boost? (in which
> case this issue just disappears)
Boost doesn't have any ABI stability.
- --
Ciaran McCreesh
-BEGIN PGP SIGNATURE--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19/01/12 03:27 AM, "Paweł Hajdan, Jr." wrote:
> On 1/19/12 9:05 AM, Johannes Huber wrote:
>> Summary of the comments: 1) Ebuilds should always pick the latest
>> boost version. 2) Boost should be compared to gcc, python, ruby
>> etc
>>
>> [1] htt
On 1/19/12 9:05 AM, Johannes Huber wrote:
> Summary of the comments:
> 1) Ebuilds should always pick the latest boost version.
> 2) Boost should be compared to gcc, python, ruby etc
>
> [1] https://bugs.gentoo.org/show_bug.cgi?id=335108
Right, Tiziano Müller's (dev-zero) comments are pretty cle
Hello,
a user submitted a bug[1] that cmake always select the latest boost. We the
kde team as cmake maintainer found a solution to respect the (e)selected
boost. The patched version is not in tree yet, because after my blog post[2]
about this issue a discussion in the bug starts.
Summary of t
