Date: Mon, 23 Jul 2012 20:04:44 -0400 From: "Jason E. Hale" <bsdkaffee@gmail.com> To: Baptiste Daroussin <bapt@freebsd.org> Cc: Max Brazhnikov <makc@freebsd.org>, Doug Barton <dougb@freebsd.org>, 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: <1430411.QqeotQn32O@mocha.verizon.net> In-Reply-To: <20120723205034.GR77496@ithaqua.etoilebsd.net> References: <D0056D18EAAD41119F26D0715FA52FB6@Rivendell> <1766706.FQA5Z9D0Zj@mercury.ph.man.ac.uk> <20120723205034.GR77496@ithaqua.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, July 23, 2012 20:50:34 Baptiste Daroussin wrote: > Here is a plan for pkg-config, I hope it will statisfy everyone. > > 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. > > Hopefully we have a viable alternative. > > What I will do is : > step 1/ introduce a new pkgconf port (https://github.com/nenolod/pkgconf) > which is 100% compatible with pkg-config and considers any incompatibility > as a bug. > > along with this, I will introduce a new MACRO: > http://people.freebsd.org/~bapt/USE_PKGCONFIG.diff > > USE_PKGCONFIG= yes or USE_PKGCONFIG= build > will bring pkgconf only has a build dependency > USE_PKGCONFIG= run > > will bring pkgconf has a run dependency (some things like ruby wrapper or > perl wrapper) > > USE_PKGCONFIG= both > will bring both run and build deps. > > Why a MACRO, because some ports may need en environnement variable in > CONFIGURE_ENV > PKG_CONFIG=pkgconf do work correctly. > > the USE_GNOME= pkgconfig will be automatically add USE_PKGCONFIG= both > > Yeah sorry for step one will keep pkgconf in both dependencies. > > This is necessary because too much ports rely on one of their deps bringing > pkgconfig, and this concerns about 4k+ ports. > > All the gnome one (mostly), all the xorg one (xproto bring pkgconfig) most > of the gtk ones, most of things depending on libxml2 and curl, from what I > have seen. > > step 2/ advertise the maintainers to stop using USE_GNOME= pkgconfig but > rather switch to USE_PKGCONFIG, and do it actively. > > setp 3/ drop USE_GNOME= pkgconfig from bsd.gnome.mk > > 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 your > port. > > regards, > Bapt I think it might be a good idea to factor out the pkg-config hacks provided by USE_GNOME=gnomehack as well, and expand it to work with CMake (or other build systems if needed). Most ports that install .pc files must be fixed to install them in libdata instead of lib. Jason E. Hale
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1430411.QqeotQn32O>