Re: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
2009/1/12 Jeremy Messenger me...@cox.net I rather to put only a version and fix the rest port. With that include/boost-134 hack is going to require hack in every port that depend on it. Cheers, Mezz Yes, all ports that depend on old boost require modification anyway. I'm just trying to find the simplest way to resolve this issue. Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
2009/1/11 Pav Lucistnik p...@freebsd.org Alexander Churanov píše v ne 11. 01. 2009 v 21:38 +0300: I'll carry out this experiment. Let's see if there's an easy way to make all the ports respect it, say, if it would mean just modifying pkg-config output. If it's non-trivial, we'll have to go with two conflicting ports. I want to run an experimental package build with new boost, to see how many ports will still need the old one. Is the patch on rapidshare (ports/129241) still valid? Or is there a new patch you want to send me? -- Pav Lucistnik p...@oook.cz p...@freebsd.org One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. Yes, that's the final patch. All uploaded patches are the same. I'll look into pkg-plist again. Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
Le Dim 11 jan 09 à 0:25:54 +0100, Pav Lucistnik p...@freebsd.org écrivait : 1) rename devel/boost to devel/boost-134 2) switch all ports depending on devel/boost to devel/boost-134 3) check-in boost-1.37 as devel/boost 4) have enough time to fix applications depending on boost-1.34 one-by-one This introduces another level of indirection - a common way to solve issues like that That's certainly a possibility -- but can two boost versions coexist in a single system? I don't know, but I know at least one port which is broken and cannot be fixed, because the required upgrade needs a newer boost (cad/freecad). Regards, -- Th. Thomas. pgp3I6QdIFiha.pgp Description: PGP signature
Re: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
2009/1/11 Pav Lucistnik p...@freebsd.org That's certainly a possibility -- but can two boost versions coexist in a single system? That's a real problem. To my mind there are no problems for shared libraries, but for header files the suggested solution would require placing headers under /usr/local/include/boost-134/boost and modify all ports' build processes to include /usr/local/include/boost-134 in a search path. I'll carry out this experiment. Another thing I've heard about port versioning is that Gentoo Linux handles different versions of the same port installed on a system. Probably, it's a good idea to examine how they do that slotting. Sincerely, Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
Alexander Churanov píše v ne 11. 01. 2009 v 21:38 +0300: 2009/1/11 Pav Lucistnik p...@freebsd.org That's certainly a possibility -- but can two boost versions coexist in a single system? That's a real problem. To my mind there are no problems for shared libraries, but for header files the suggested solution would require placing headers under /usr/local/include/boost-134/boost and modify all ports' build processes to include /usr/local/include/boost-134 in a search path. I'll carry out this experiment. Let's see if there's an easy way to make all the ports respect it, say, if it would mean just modifying pkg-config output. If it's non-trivial, we'll have to go with two conflicting ports. I want to run an experimental package build with new boost, to see how many ports will still need the old one. Is the patch on rapidshare (ports/129241) still valid? Or is there a new patch you want to send me? -- Pav Lucistnik p...@oook.cz p...@freebsd.org One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
On Sun, 11 Jan 2009 12:38:10 -0600, Alexander Churanov alexanderchura...@gmail.com wrote: 2009/1/11 Pav Lucistnik p...@freebsd.org That's certainly a possibility -- but can two boost versions coexist in a single system? That's a real problem. To my mind there are no problems for shared libraries, but for header files the suggested solution would require placing headers under /usr/local/include/boost-134/boost and modify all ports' build processes to include /usr/local/include/boost-134 in a search path. I rather to put only a version and fix the rest port. With that include/boost-134 hack is going to require hack in every port that depend on it. Cheers, Mezz I'll carry out this experiment. Another thing I've heard about port versioning is that Gentoo Linux handles different versions of the same port installed on a system. Probably, it's a good idea to examine how they do that slotting. Sincerely, Alexander Churanov -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
2009/1/10 Pav Lucistnik p...@freebsd.org Are you also willing to fix all the applications that will not work with the new version of boost? I understand that's the only concern preventing new boost from being committed. Why not fix it in several steps? : 1) rename devel/boost to devel/boost-134 2) switch all ports depending on devel/boost to devel/boost-134 3) check-in boost-1.37 as devel/boost 4) have enough time to fix applications depending on boost-1.34 one-by-one This introduces another level of indirection - a common way to solve issues like that Sincerely, Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
Alexander Churanov píše v ne 11. 01. 2009 v 01:07 +0300: 2009/1/10 Pav Lucistnik p...@freebsd.org Are you also willing to fix all the applications that will not work with the new version of boost? I understand that's the only concern preventing new boost from being committed. Why not fix it in several steps? : 1) rename devel/boost to devel/boost-134 2) switch all ports depending on devel/boost to devel/boost-134 3) check-in boost-1.37 as devel/boost 4) have enough time to fix applications depending on boost-1.34 one-by-one This introduces another level of indirection - a common way to solve issues like that That's certainly a possibility -- but can two boost versions coexist in a single system? -- Pav Lucistnik p...@oook.cz p...@freebsd.org Alignment: Neutral Greedy signature.asc Description: Toto je digitálně podepsaná část zprávy
STILL OPEN: ports/129226: update devel/boost from 1.34.1 to 1.37
Hi folks, The issue ports/129226 was filed at November, 27 2008 and remains open at present. The issue text contains a link to the patch I've created for the devel/boost port. The problem is that current port version is too old. Boost team is going to release 1.38 on the 31st of January. I have skills, time, equipment and willing for porting that new version to FreeBSD in time. I've already started with current boost-1.38. However I'm not sure that creating patches for 1.38 in time is valuable provided that it's not possible to check them in. Guys, is any other help necessary to make 1.37 ported? Sincerely, Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
