Date: Sat, 16 Jul 2016 18:26:05 +0200 From: Baptiste Daroussin <bapt@freebsd.org> To: Atomic Beef <teddyg522@gmail.com> Cc: freebsd-pkg@freebsd.org Subject: Re: State of Provides/Requires Message-ID: <20160716162605.flotxo3hdohla35z@ivaldir.etoilebsd.net> In-Reply-To: <CAK%2B0_cD6PdJn1nv5%2BT=0v1zc-MjAH%2Ba3WHGGKWm2TyLtVrts1A@mail.gmail.com> References: <CAK%2B0_cD%2B3E1buHURDNJd-RD_W0Hs=0enqXzag5K5VYizb5rkCw@mail.gmail.com> <20160716151339.lvco3nmctrrk6h7s@ivaldir.etoilebsd.net> <CAK%2B0_cD6PdJn1nv5%2BT=0v1zc-MjAH%2Ba3WHGGKWm2TyLtVrts1A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--wrrfgfoe6unnednm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 16, 2016 at 12:00:15PM -0400, Atomic Beef wrote: > On Sat, Jul 16, 2016 at 11:13 AM, Baptiste Daroussin <bapt@freebsd.org> > wrote: >=20 > > Provides/Requires has been added in pkg around 1.4 (iirc) > > > > They are not perfect and we would prefer to use what we call flexible > > dependencies instead. that said flexible dependencies are not any close= to > > be > > implemented. So I think we should use current provides/requires mechani= sm > > in the > > mean time. > > > > To use them the only issue in on the ports tree itself > > > > Best regards, > > Bapt > > > What are the differences between flexible dependencies and the current > provides/requires implementation? What needs to be done to the ports tree > to allow for the use of provides/requires? Current provides/requires are basic keywords that should exactly match Flexible dependencies is a formula like php > 9 < 9.5, libmysql.so.X; gmake =3D 12 All the current form of dependencies (shlibs, provides/requires, regular de= ps) can be expressed in a single form without the need of special treatment. To implements in ports the goal is to add everywhere in the ports things informations that will be exposed in the manifest as provides: [ X, Y, Z] and a way to express when requiring X, the default build package will be li= bX but will not be registered as a deps because the requires line in the manif= est will handle the deps. Noone really started working on the port side. Bapt --wrrfgfoe6unnednm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXimAbAAoJEGOJi9zxtz5a9+EQANvK4s6DtUjSVxJyQrwec/ra xbZ29AF/tPDFXN4qBEfphbF9+Qxmt8UkyB6j1J5CC/ZuxbYz2XBlk3kAz9TRZod1 SorABl5sXm285S/rIhHdicOy2VySl4SGz/gGp5HY3RM8JdA8TsF+FHBXlZnkE7Ia 4+9nl5P4OcteGAVBQzi+VYfpS8uqskDiKd0EB7KXxnfLLsM87OmHGoVGmEee0u4/ XsSzl+RGsIQE2Uo7LRWXtpZ3KNSLrLZlmi8it6MbFzg+/7K/eORo71uHjR8FwwdP RJjDLR+38/MPZ5nyAiz4AnF77P9vDMmtYMMIn1aqj89rtMMrvoZ/aX9DAUU32HrF 0GUj0bUVHSFeHix/ruJy5CW73A0tmxy9VmM8pCUB9Aiz2/WuVSoQcIcRI21S9JQM 1SihsrXbNbuMNVb90BW2G/h2LSUWEhRIKpQK9gdyEqmU/7dUdg2OJNsqKHCb93Sq twU6RaloRWwN6ZJlEYZ2+4SRDYy6WArvvD9JpupDVPNbVSPvt8yHjCj5wfoxaJ5k IViOF75SG5OC11JX0wl5EKI5ol1f2Hun4jgPgtsln6GYqUQ1SMbgehf4lrZavT9b 1/VCXJUIMPZd0F9lb2HBfy3mbbHcuhLWAONN0ZC57moLkG8EqkbueJ0JOpb4f27D 7HwbPme95H6A71lyR+eh =BpiK -----END PGP SIGNATURE----- --wrrfgfoe6unnednm--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160716162605.flotxo3hdohla35z>