Date: Thu, 20 Apr 2017 23:21:53 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Koop Mast <kwm@FreeBSD.org> Cc: arch@FreeBSD.org, ports@FreeBSD.org, portmgr@FreeBSD.org Subject: Re: manpath change for ports ? Message-ID: <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> In-Reply-To: <1492723094.55896.22.camel@FreeBSD.org> References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--akklfd3ecjwxpoxg Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 20, 2017 at 11:18:14PM +0200, Koop Mast wrote: > On Tue, 2017-03-07 at 00:56 +0100, Baptiste Daroussin wrote: > > Hi all, > >=20 > > I would like to propose a change in the localbase hier for ports > >=20 > > I think we should add /usr/local/share/man in the manpath along with > > at first > > and maybe instead of in long term. > >=20 > > The reason is: > > - /usr/local/share/man seems more consistent to me with base which > > have: > > =A0 /usr/share/man > > - It will remove lots of patches from the ports tree where were we > > need to patch > > =A0 upstream build system to install in a non usual path. > >=20 > > My proposal is to add to the manpath /usr/local/share/man in default > > man(1) > > command in FreeBSD 12 (MFCed to 11-STABLE) > >=20 > > and either provide an errata for 11.0/10.3 or a > > /usr/local/etc/man.d/something.conf via a port or something like that > > for those > > two, what do you think? > >=20 > > For the same reason I would like to allow porters to stop patching > > (with pathfix > > or anything else) the path for pkgconfig files and allow > > /usr/local/lib/pkgconfig along with the current > > /usr/local/libdata/pkgconfig:/usr/libdata/pkgconfig > >=20 > > Which will also remove tons of hacks from the ports tree. > >=20 > > What do you think? > >=20 > > Best regards, > > Bapt >=20 > Hello, >=20 > I recently committed the USES for the meson build system to ports. This > USES configures the meson build system with some default variables > which includes the location of the man pages. This setting is just a > flag to the meson command so it easy to change. >=20 > Meson also handles the generation and installation of pkg-config files > that a port wants. The problem is that this is handled by the script > itself and there is no way to configure it, so we need to hack the > meson port to change it from lib/pkg-config to libdata/pkg-config like > we currently are using. (1) Or add a hack to meson.mk to move the pkg- > config to the right location (evil++ imho). >=20 > My point I want to make is that currently there is only 1 port build > via the meson system (graphics/graphene). Should we change man/pkg- > config file locations now, it very easy. If we want to change them > later we will need to mass bump every meson build port. It is important > to note that GStreamer and GNOME are moving over to using meson instead > of autotools and that Wayland, Xorg en Mesa are exploring want is > needed to make the switch. So I think it important that the decision > what to do is done now and that we stick with it. >=20 > Reading the rest of the thread it seems nobody is really against the > proposed change of man and pkg-config path's. So how does one submit a > policy change like this? I'm also not sure I'm the right person to push > this, I just got back from a break and I don't want to really deal with > something super high profile right away. >=20 > -Koop >=20 > (1) I would like to see lib/pkg-config back in the search path of > pkgconf since that means I don't have to do a crash course python > programming. Would be nice is portmgr can step on this, let's reduce this discussion for= now on pkgconf. Best regards, Bapt --akklfd3ecjwxpoxg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlj5JnEACgkQY4mL3PG3 PloiNBAAvrZY2nONkMQTlWiOVr+3QBtR63PPEPFtzVBZnGpapQBQW8V/99n06gHV 9ibuniGCPqjqrpNWbPyKmAiX+D759UbfoqzYT3Cx+sz0v/SxUEn249p/eiHG3PTi EJ/vYIK76WeVCMLqmfXdy0Rdd09elWzW5A45oqRb8HCP0azAlmblcXz8a83rYME2 sf3ve1BgSsG/zvLCXvzdW5BcsX8FbasfDPEtMP1MRmRAxQaZnAeViViNBY+bQwAL moipmmtyrgbgVjLGGekfNdMvZnLuToVRfrf6otrQCj4G/VhnT8YnQ7yEAE9p6vh3 BCEAK/Rf2oz58NytEe2tyW9FjDyOJ9Ep/IhzQM1r/7pTe9cq4Fxv21qAXmiOltUB +y4cF+kSjKbOH8Nm9iUpO/CLr9Ceg7iWKWxvmsIPAXd9Ye5k6j6U4b2OIBLhFPz9 Wj72zr0UQr7Da7gaUBMzGYAJ5OXvGXA98/rQW2Oq9wLxZ16tt0PiGM+yRP39qPpu wEAvz3ZZG8/u1qnjSGk6Pv4Jv21XmAy3cFXlJbUmVwoK8bKb1DDw24g27B/IWYjT JNBlfG1Oq/SgQzCQaRbcXDLu2R1MjzrfxGgImUGXP1ZMGunvZFXB4VKbp+xdcmhl vnO0Gp6sGrJm5cStBPdd/rYPRDFb+PD8oJ1Dtna58Lcy/dCeqvA= =gOrr -----END PGP SIGNATURE----- --akklfd3ecjwxpoxg--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170420212153.cawvn4xsxuwuebfu>