Date: Tue, 24 Jul 2012 06:54:35 +0000 From: Baptiste Daroussin <bapt@freebsd.org> To: "Jason E. Hale" <bsdkaffee@gmail.com> Cc: kde@freebsd.org, freebsd-gnome@freebsd.org, kwm@freebsd.org, Kimmo Paasiala <kpaasial@gmail.com>, Jeremy Messenger <mezz.freebsd@gmail.com>, ruby@freebsd.org, Edwin Groothuis <edwin@mavetju.org>, Scot Hetzel <swhetzel@gmail.com>, freebsd-ports@freebsd.org, gnome@freebsd.org Subject: Re: How to remove erroneous deps from pkgng Message-ID: <20120724065435.GS77496@ithaqua.etoilebsd.net> In-Reply-To: <1430411.QqeotQn32O@mocha.verizon.net> References: <D0056D18EAAD41119F26D0715FA52FB6@Rivendell> <1766706.FQA5Z9D0Zj@mercury.ph.man.ac.uk> <20120723205034.GR77496@ithaqua.etoilebsd.net> <1430411.QqeotQn32O@mocha.verizon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--tqSMaTz1cCSspCQ4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 23, 2012 at 08:04:44PM -0400, Jason E. Hale wrote: > On Monday, July 23, 2012 20:50:34 Baptiste Daroussin wrote: > > Here is a plan for pkg-config, I hope it will statisfy everyone. > >=20 > > First we need to get rid of pkg-config, since 0.26 we can't boostrap it > > anymore because it depends on glib which depends on pkg-config. > >=20 > > Hopefully we have a viable alternative. > >=20 > > What I will do is : > > step 1/ introduce a new pkgconf port (https://github.com/nenolod/pkgcon= f) > > which is 100% compatible with pkg-config and considers any incompatibil= ity > > as a bug. > >=20 > > along with this, I will introduce a new MACRO: > > http://people.freebsd.org/~bapt/USE_PKGCONFIG.diff > >=20 > > USE_PKGCONFIG=3D yes or USE_PKGCONFIG=3D build > > will bring pkgconf only has a build dependency > > USE_PKGCONFIG=3D run > >=20 > > will bring pkgconf has a run dependency (some things like ruby wrapper = or > > perl wrapper) > >=20 > > USE_PKGCONFIG=3D both > > will bring both run and build deps. > >=20 > > Why a MACRO, because some ports may need en environnement variable in > > CONFIGURE_ENV > > PKG_CONFIG=3Dpkgconf do work correctly. > >=20 > > the USE_GNOME=3D pkgconfig will be automatically add USE_PKGCONFIG=3D b= oth > >=20 > > Yeah sorry for step one will keep pkgconf in both dependencies. > >=20 > > This is necessary because too much ports rely on one of their deps brin= ging > > pkgconfig, and this concerns about 4k+ ports. > >=20 > > All the gnome one (mostly), all the xorg one (xproto bring pkgconfig) m= ost > > of the gtk ones, most of things depending on libxml2 and curl, from wha= t I > > have seen. > >=20 > > step 2/ advertise the maintainers to stop using USE_GNOME=3D pkgconfig = but > > rather switch to USE_PKGCONFIG, and do it actively. > >=20 > > setp 3/ drop USE_GNOME=3D pkgconfig from bsd.gnome.mk > >=20 > > when switching to USE_PKGCONFIG becare full about the ports that depend= on > > your ports to make sure, it doesn't expect pkgconfig being brought by y= our > > port. > >=20 > > regards, > > Bapt >=20 > I think it might be a good idea to factor out the pkg-config hacks provid= ed by=20 > USE_GNOME=3Dgnomehack as well, and expand it to work with CMake (or other= build=20 > systems if needed). Most ports that install .pc files must be fixed to= =20 > install them in libdata instead of lib. >=20 > Jason E. Hale That is a good idea, good be done after the switch to pkgconf. It will need some volunteer :) regards, Bapt --tqSMaTz1cCSspCQ4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlAORqsACgkQ8kTtMUmk6EzitACaAroTABdRe8vqOaQUhC/AGg9c j8MAoLHHHW8WSDSq64Zx6/yBF/Hrtc8R =EvE3 -----END PGP SIGNATURE----- --tqSMaTz1cCSspCQ4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120724065435.GS77496>