Date: Sat, 23 Aug 2014 09:14:52 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: question about "pkg install" Message-ID: <53F84D7C.70101@FreeBSD.org> In-Reply-To: <20140823074040.GY9400@home.opsec.eu> References: <53F7BE28.2030807@rcn.com> <20140823074040.GY9400@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --AvSQ3n7WEg2QiE6rxRE693o8eAbQtTC2a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 23/08/2014 08:40, Kurt Jaeger wrote: >> I have a program (several, actually) I need to install from the >> > generic package repository. >> > These programs depend on openldap-client; however I have >> > openldap-sasl-client installed. In my experience the two have been >> > interchangeable when compiling from ports. >> > Is there a way to tell 'pkg install' "Yeah, I know it >> > says openldap-client, but the same version of >> > openldap-sasl-client satisfies the dependency"? Or do I just use 'p= kg >> > install -M' and hope everything works? > I had this issue in the past, too, and am not aware of a solution. There isn't a good solution for this right now if you're using the packages from the official FreeBSD repositories. You get the default dependency chain which is baked into the packages. Which means openldap-client rather than openldap-sasl-client[*]. If you need to change options for various ports, then the best solution is to compile your own. Give poudriere a go -- it is surprisingly easy and unstressful to use. Build yourself a repo with your customized ports in it and away you go. We do have plans for improving the ports behaviour in this reguard. Dependencies based on Provides/Requires/Conflicts should help a lot, as will sub-packages and dependency version-ranges. This stuff is all on the roadmap, but there's a lot of work to do to get from here to there, so don't expect it to all start magically working tomorrow. Cheers, Matthew [*] In this case openldap-client and openldap-sasl-client are clearly API compatible, since on compilation, it's not a problem to swap from one to the other. The question when using binary packages is if they are ABI compatible, which is a whole different kettle of fish. --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --AvSQ3n7WEg2QiE6rxRE693o8eAbQtTC2a Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) iQJ8BAEBCgBmBQJT+E2EXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkAT9voP/10ZSrUyD+ytbQtlW4pf8w7I hgOjhBZGdhumB081jx6OC7ty4S38yJJcpkann0zMeNQ93jxTP8jcdr+Zg58Q0H+g bag8KbZjHW7MJDIJ0fQG9JGlPju1vVEy46LoCIaUPBfaSowDubUpVUSXFxE3AhBR 9O9cmhSBmbjOM7XyQrUKlHXiKeV+3BOaYQpT+0Rwma4nU/m52nrlNkA7/yWwiziQ bzs9m6Lf/jIkxTm/5BsWIDO/6JBiNMn5wJWZfhlwaAdgARlHdVE1H5QZFpfFHsth wbBrK5Anr9nCupOyML4P1RvSRxhSMbfWBgv2imvYLbLW52tEwpCVq8M+1F3DGkfG 7jSt2CTM58u1gwygWzaGnRpf6zAgwIDS5tw319N3ypOK2TRjUYgHC5+q37LIx8pK coxvK1Qn8Nx4uHvH7xHj+uSu/mGzMQi8DZLLCBKg+/lmvOBzjJ2vPtFfgch9wgOZ 1G639xe5SxIBAz0Q33dAgFQHUsBKaQ2HWsFC2nS7khJ1z2FlBn4IhheqmRQ5+j5Y CAi3lS0RREQ+pI1sxlVcRa+sgEcD12oKmAFKz8iDPoPAnXlwsFLhTtW5VAo2Mydm 100amW7VzKRmIVG7Qu5BJ+S1YtOOEw5mj9KfonzaPg9KpZ/xi5b2kAvg23Wxocu8 pwQgXxUefUTN9Mm1jhLg =JcWN -----END PGP SIGNATURE----- --AvSQ3n7WEg2QiE6rxRE693o8eAbQtTC2a--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53F84D7C.70101>