Date: Tue, 05 May 2020 13:46:30 -0700 From: Chris <portmaster@BSDforge.com> To: Leander Schaefer <info@NetOcean.de> Cc: John Berry <John.Berry@NetOcean.de>, <freebsd-ports@freebsd.org> Subject: Re: Poudriere - Compile ALL Ports Message-ID: <43d5e0710e147420e3cdcfa1342122f7@udns.ultimatedns.net> In-Reply-To: <fc70283e-1892-aeb8-6dfb-a8e6e269559a@NetOcean.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 5 May 2020 22:38:36 +0200 Leander Schaefer info@NetOcean=2Ede said > Hello, >=20 > I have been dealing with Poudriere for quite a while and one of the most= =20 > issues I have is, that I have ports which won't compile along with=20 > another=2E Reason is mostly something like: >=20 > pkg-static: ImageMagick7-7=2E0=2E10=2E6 conflicts with ImageMagick6-6=2E9=2E11=2E6,1= =20 > (installs files into the same place)=2E Problematic file:=20 > /usr/local/bin/Magick++-config >=20 > So in other words a newer version is going to place its binaries etc=2E=20 > into the same place as the previous version=2E I have read and used=20 > something like: >=20 > # Build several PHP versions parallel on the same server: > # https://github=2Ecom/freebsd/poudriere/issues/602 > PHP_ALT=3Dphp56 php70 php71 php72 php73 > =2Efor port in ${PHP_ALT} > =2Eif ${=2ECURDIR:M*/ports*/*/${port}*} > DISABLE_CONFLICTS=3DYES > PREFIX=3D/usr/local/${port} > PHPBASE=3D/usr/local/${port} > LOCALBASE=3D/usr/local > CONFIGURE_ARGS+=3D--datadir=3D/usr/local/${port}/share > CONFIGURE_ARGS+=3D--bindir=3D/usr/local/${port}/bin > CONFIGURE_ARGS+=3D--with-config-file-scan-dir=3D/usr/local/${port}/etc/ph= p > #CONFIGURE_ARGS+=3D--with-php-config=3D/usr/local/${port}/bin/php=2Econf > #CONFIGURE_ARGS+=3D--with-iconv=3D/usr/local > #CONFIGURE_ARGS+=3D--with-pcre-dir=3D/usr/local > =2Eendif > =2Eendfor >=20 > But I was wondering: How is the FreeBSD Team dealing with this, when=20 > they compile their packages for the public repository? Because we only=20 > use one official repository and all packages are there =2E=2E=2E some even=20 > with differet options enabled=2E So how to deal with this? How can I=20 > compile the entire ports tree without issues and build a repository of=20 > it and some packages even with different options? Lets say one OpenLDAP= =20 > with SASL and another one with SASL? The only way I was able to do this= =20 > was building it in separate repositories=2E >=20 > Thanks I use Jails which helps weed out some of the conflicts=2E That is different jails for different (port) options that *may* cause conflict=2E Also ports-mgmt/synth is pretty damn clever about sorting out conflicts=2E However, I have no direct knowledge on how the pkg build admins deal with this=2E But just thought I'd share some alternate avenue(s) FWIW=2E :-) >=20 > _______________________________________________ > freebsd-ports@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd=2Eorg"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43d5e0710e147420e3cdcfa1342122f7>