Date: Fri, 21 Apr 2017 00:29:15 +0200 From: Mathieu Arnold <mat@FreeBSD.org> To: Baptiste Daroussin <bapt@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: <f1ed7679-fc27-9bba-dbb8-d070a603b591@FreeBSD.org> In-Reply-To: <20170420222154.wtk5zvprn2g5b6ny@ivaldir.net> 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> <20170420222154.wtk5zvprn2g5b6ny@ivaldir.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --M6ruqCFds9cMr1iEvV2uVecaNHTDUjGxn Content-Type: multipart/mixed; boundary="u6useOiVKf44ivSEJpPrGEuWSVXgnjswi"; protected-headers="v1" From: Mathieu Arnold <mat@FreeBSD.org> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: ports@FreeBSD.org, Koop Mast <kwm@FreeBSD.org>, arch@FreeBSD.org, portmgr@FreeBSD.org Message-ID: <f1ed7679-fc27-9bba-dbb8-d070a603b591@FreeBSD.org> Subject: Re: manpath change for ports ? 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> <20170420222154.wtk5zvprn2g5b6ny@ivaldir.net> In-Reply-To: <20170420222154.wtk5zvprn2g5b6ny@ivaldir.net> --u6useOiVKf44ivSEJpPrGEuWSVXgnjswi Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Le 21/04/2017 =C3=A0 00:21, Baptiste Daroussin a =C3=A9crit : > On Fri, Apr 21, 2017 at 12:18:53AM +0200, Mathieu Arnold wrote: >> Le 21/04/2017 =C3=A0 00:16, Baptiste Daroussin a =C3=A9crit : >>> On Fri, Apr 21, 2017 at 12:13:52AM +0200, Mathieu Arnold wrote: >>>> Le 20/04/2017 =C3=A0 23:21, Baptiste Daroussin a =C3=A9crit : >>>>> 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 w= ith >>>>>>> at first >>>>>>> and maybe instead of in long term. >>>>>>> >>>>>>> The reason is: >>>>>>> - /usr/local/share/man seems more consistent to me with base whic= h >>>>>>> have: >>>>>>> /usr/share/man >>>>>>> - It will remove lots of patches from the ports tree where were w= e >>>>>>> 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 defa= ult >>>>>>> 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 = that >>>>>>> for those >>>>>>> two, what do you think? >>>>>>> >>>>>>> For the same reason I would like to allow porters to stop patchin= g >>>>>>> (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.= 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. >>>>>> >>>>>> Meson also handles the generation and installation of pkg-config f= iles >>>>>> that a port wants. The problem is that this is handled by the scri= pt >>>>>> 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). >>>>>> >>>>>> My point I want to make is that currently there is only 1 port bui= ld >>>>>> 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 impo= rtant >>>>>> to note that GStreamer and GNOME are moving over to using meson in= stead >>>>>> of autotools and that Wayland, Xorg en Mesa are exploring want is >>>>>> needed to make the switch. So I think it important that the decisi= on >>>>>> what to do is done now and that we stick with it. >>>>>> >>>>>> Reading the rest of the thread it seems nobody is really against t= he >>>>>> proposed change of man and pkg-config path's. So how does one subm= it 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. >>>>>> >>>>>> -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 discus= sion 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? wha= t 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. >> > ok a point for you there :) I have no problems having lib/pkgconfig added to the search path so that people who build stuff manually have their .pc files in a place where pkg-config can read them, but I really do not want the ports to install them in more than one place. My PR solves that problem, all the ports will forcibly end up in libdata/pkgconfig, we could even drop USES=3Dpathfix. --=20 Mathieu Arnold --u6useOiVKf44ivSEJpPrGEuWSVXgnjswi-- --M6ruqCFds9cMr1iEvV2uVecaNHTDUjGxn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJY+TY8XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85I2ukP/iewLpTKlpzI/O9A6eNDmfJv QsOH7t3iK9tc/UcnP45RxCi4ZMqTD4xY4wnKnSnlrQDoprxnVxkpU3cmGAX3RgWa VH2sbsNIKh1TmDoZNv4Bk6qDNd+g/gHYcd74s7UuMIh+iXX0R4vF/nI7Mket+inl UvAxmiLk6rez/a7RQG36wzmds4ftMoJtd09MMY2utP7DQEj6yycI/N7osgdXCo4r /cS+sELUBHlLY0eR5Alje9SBSfA66HzMojW04Z0uiQb5xhJyqKzHr14vz7Ucqfqd bld7iHwy2O/FGjoISANoVoWPJKyzDMW/AJdWI07tcHhnEk4TgsYxaf4XyHbvkfuI hSqkZ5XGHcY9djW+qmE2TQr7c5iVPMu16GxqRZNrVhmRWGayaQGXFvdiIGNHAGer F+kcZuAP8j8rJeqoSoTs0g7xk+HtORVSkLaZNtRQNjMP/FoxnSaaqwSF+Jpy1mj/ HRmH3TxPXhp0vnfmMFu/Wby6AmNfjEPRGOpPjZYgV6F9Or5YhhAFUfHCVjTRFr55 j3Vvdn9GBlsNAfDGl8o7R1COkpyaw4m4caBAsFfAs3k4Vp0GewDW7yPh/tnKAopJ CRWXuiZTb+8EnMO4xX7RwMqNECXekf/s351pyF46e0JfkVa2g8A5pUjs9m0Mjx3e Forxsjpu98vCEzcowu8m =twSm -----END PGP SIGNATURE----- --M6ruqCFds9cMr1iEvV2uVecaNHTDUjGxn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f1ed7679-fc27-9bba-dbb8-d070a603b591>