Date: Fri, 21 Apr 2017 00:21:54 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Mathieu Arnold <mat@FreeBSD.org> Cc: ports@FreeBSD.org, Koop Mast <kwm@FreeBSD.org>, arch@FreeBSD.org, portmgr@FreeBSD.org Subject: Re: manpath change for ports ? Message-ID: <20170420222154.wtk5zvprn2g5b6ny@ivaldir.net> In-Reply-To: <ef3b557f-7798-5b57-7c31-26b84d5fa8af@FreeBSD.org> References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> <dee320db-98d5-177c-839f-68225e56a1ae@FreeBSD.org> <20170420221631.yxukhuwo4tn7blte@ivaldir.net> <ef3b557f-7798-5b57-7c31-26b84d5fa8af@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--jbc5mn23tydn6e5r Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 21, 2017 at 12:18:53AM +0200, Mathieu Arnold wrote: > Le 21/04/2017 =E0 00:16, Baptiste Daroussin a =E9crit : > > On Fri, Apr 21, 2017 at 12:13:52AM +0200, Mathieu Arnold wrote: > >> Le 20/04/2017 =E0 23:21, Baptiste Daroussin a =E9crit : > >>> 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, > >>>>> > >>>>> I would like to propose a change in the localbase hier for ports > >>>>> > >>>>> I think we should add /usr/local/share/man in the manpath along with > >>>>> at first > >>>>> and maybe instead of in long term. > >>>>> > >>>>> The reason is: > >>>>> - /usr/local/share/man seems more consistent to me with base which > >>>>> have: > >>>>> /usr/share/man > >>>>> - It will remove lots of patches from the ports tree where were we > >>>>> need to patch > >>>>> upstream build system to install in a non usual path. > >>>>> > >>>>> My proposal is to add to the manpath /usr/local/share/man in default > >>>>> man(1) > >>>>> command in FreeBSD 12 (MFCed to 11-STABLE) > >>>>> > >>>>> 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 th= at > >>>>> for those > >>>>> two, what do you think? > >>>>> > >>>>> 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 > >>>>> > >>>>> Which will also remove tons of hacks from the ports tree. > >>>>> > >>>>> What do you think? > >>>>> > >>>>> Best regards, > >>>>> Bapt > >>>> Hello, > >>>> > >>>> I recently committed the USES for the meson build system to ports. T= his > >>>> 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. > >>>> > >>>> Meson also handles the generation and installation of pkg-config fil= es > >>>> 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 li= ke > >>>> we currently are using. (1) Or add a hack to meson.mk to move the pk= g- > >>>> config to the right location (evil++ imho). > >>>> > >>>> 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 import= ant > >>>> to note that GStreamer and GNOME are moving over to using meson inst= ead > >>>> 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. > >>>> > >>>> 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 p= ush > >>>> this, I just got back from a break and I don't want to really deal w= ith > >>>> something super high profile right away. > >>>> > >>>> -Koop > >>>> > >>>> (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 discussi= on for now > >>> on pkgconf. > >> > >> I am waiting on an exp-run to fix this once and for all. > >> > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218067 > >> > >> When that is committed, anything can be added to the path pkgconfig > >> searches, ports will always install it in the right place. > >> > > Sorry but why? why not moving libdata/pkgconfig to lib/pkgconfig? what = is the > > rationale? > Because a lot of build software know that on FreeBSD, the .pc file go in > libdata/pkgconfig. If we move to some other place, we'll have a > USES=3Dpathfixmore for the next 25 years until everyone understands we > moved it some place else. >=20 ok a point for you there :) Bapt --jbc5mn23tydn6e5r Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlj5NIIACgkQY4mL3PG3 PloiJw/9GYDGgxSamCyELEIfl+BkKlI2qqOBAo3xUkidXNPEVmmsIM/pbEc1oXzF 0ZArbRQSpkLHVaJwIxIF7ITfPtcDexgfbLBNDHFcp+VNahVdL6Zja+0ut1gwUboK zwszn3EbyKoKFh+dz1yG0Gcf3obCmTyqXlA4Oh/SYEaUT3jWZhkp1CRDB1E9Mu1D KnNxxQ2mf85wknxBwPVxIiRf8benyciB87dYPXkVNZru7LpFfLvUpP8f96cKEteb 6WT9G1gPnlR4zfDDjdkul9JUEQ5Dsk2PtMv6ILpwS7lPrR5/3mDXIMAhRn9H/feW jKOL8XGpaPN7jzSlDFw695b0qWtS64qW1oV8WrNzG7RuxkiJxuNCRIs7YcPP/diJ JbdxPiu9AgAGgRHJ8DQPAOMe3K6v2Ze5xWg3R1EQHfS7+Ra9XJvhZG42aeXzcBn4 I/ePIdyPTvfEsv/ECLgTjekz/O8S4at4rm/oHI2VX8oIfEYCroblkAl6uAldoWxL LI3AhhvBbvvgslrtw1n6TN3HdsjVzWPrkOmCuqN0uiALiLG5t3jOe7fcG1IfP2QS 3GJ0NcoxN/GS3DfJRk2A+f0DPadhHFuebZQSR9wRqr+s0Kbcew1GXOA5z2RHO1u9 VAg4jd0CCNDq/lUSvOz+UfaHrot58IYxddtz36+yPhDg4f+7pD0= =6sBy -----END PGP SIGNATURE----- --jbc5mn23tydn6e5r--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170420222154.wtk5zvprn2g5b6ny>