| 1 |
Dne Út 30. října 2012 20:24:26, Michał Górny napsal(a): |
| 2 |
> On Tue, 30 Oct 2012 11:30:16 -0700 |
| 3 |
> |
| 4 |
> Diego Elio Pettenò <flameeyes@×××××××××.eu> wrote: |
| 5 |
> > Given the amount of headaches that Boost seems to give us all, now |
| 6 |
> > thanks to the recent changes even more because Gentoo's boost is |
| 7 |
> > different from all others and no upstream default check seem to work |
| 8 |
> > correctly with it, I'm questioning the usefulness of having it slotted. |
| 9 |
> |
| 10 |
> Could you elaborate on that? I don't remember having problems with |
| 11 |
> boost.m4 or cmake's default checks unless I'm missing something which |
| 12 |
> is obvious to you. |
| 13 |
|
| 14 |
Michal, |
| 15 |
given my affiliation with libreoffice I am handling quite few sh*t about |
| 16 |
buildsystems there. |
| 17 |
|
| 18 |
Currently we have orcus/wps/visio and libreoffice itself checking for internal |
| 19 |
components of boost in the configure scripts. You basically want me to add 1 |
| 20 |
kB m4 file from some github site (aside from fact it is nicely licensed GPLv3) |
| 21 |
and change all those checks we have to confor with this m4 so they work again |
| 22 |
for Gentoo. |
| 23 |
|
| 24 |
Here let me put the emphasis on "FOR GENTOO" because no other distro on to |
| 25 |
this day had problem with the boost setup lo projects are using, and we |
| 26 |
include stuff like win and mac. |
| 27 |
|
| 28 |
My alternative for this work is to do this on gentoo side and add append |
| 29 |
cflags and libs in each pkg using the boost-utils eclass and again add more |
| 30 |
shit i have to maintain into each ebuild. |
| 31 |
|
| 32 |
> |
| 33 |
> > So given that it's a PITA for the maintainers, a PITA for the users, |
| 34 |
> > eselect boost has been shown to be a bad idea and so on ... can we just |
| 35 |
> > go back to just install it and that's about it? |
| 36 |
> |
| 37 |
> How are you going to solve the issue of a lot of packages being broken |
| 38 |
> with new boost versions? Are you volunteering to keep fixing them with |
| 39 |
> each release? |
| 40 |
|
| 41 |
Simple, as any other lib, depend on older version and possibly port it |
| 42 |
forward. |
| 43 |
If that does not work then mask and wipe. Life goes on. |
| 44 |
|
| 45 |
Do we have at least some good use case on split boost requirement? |
| 46 |
|
| 47 |
Tomas |
Archives