On Tue, Oct 30, 2012 at 3:24 PM, Michał Górny <mgo...@gentoo.org> wrote:
> On Tue, 30 Oct 2012 11:30:16 -0700 > Diego Elio Pettenò <flamee...@flameeyes.eu> wrote: > > > Given the amount of headaches that Boost seems to give us all, now > > thanks to the recent changes even more because Gentoo's boost is > > different from all others and no upstream default check seem to work > > correctly with it, I'm questioning the usefulness of having it slotted. > > Could you elaborate on that? I don't remember having problems with > boost.m4 or cmake's default checks unless I'm missing something which > is obvious to you. > > > So given that it's a PITA for the maintainers, a PITA for the users, > > eselect boost has been shown to be a bad idea and so on ... can we just > > go back to just install it and that's about it? > > How are you going to solve the issue of a lot of packages being broken > with new boost versions? Are you volunteering to keep fixing them with > each release? > It's worth noting that Boost themselves recommend developers inline the code they want to use. I've never understood why Gentoo uses a separate ebuild for it. I mean, I can understand some efficiency gains from having a single compiled copy, but it shouldn't be surprising in the least when upstream makes breaking changes in the API. -- :wq
