Date: Fri, 21 Apr 2017 00:13:52 +0200 From: Mathieu Arnold <mat@FreeBSD.org> To: Baptiste Daroussin <bapt@FreeBSD.org>, Koop Mast <kwm@FreeBSD.org> Cc: arch@FreeBSD.org, ports@FreeBSD.org, portmgr@FreeBSD.org Subject: Re: manpath change for ports ? Message-ID: <dee320db-98d5-177c-839f-68225e56a1ae@FreeBSD.org> In-Reply-To: <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> <20170420212153.cawvn4xsxuwuebfu@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) --6BetvbhbJJtKVL9x7EQK9wxNh1K9HmfI4 Content-Type: multipart/mixed; boundary="99btd0QpQ3QbTKV5eB4gnRJx9X1mfLF7K"; protected-headers="v1" From: Mathieu Arnold <mat@FreeBSD.org> To: Baptiste Daroussin <bapt@FreeBSD.org>, Koop Mast <kwm@FreeBSD.org> Cc: arch@FreeBSD.org, ports@FreeBSD.org, portmgr@FreeBSD.org Message-ID: <dee320db-98d5-177c-839f-68225e56a1ae@FreeBSD.org> Subject: Re: manpath change for ports ? References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> In-Reply-To: <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> --99btd0QpQ3QbTKV5eB4gnRJx9X1mfLF7K Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: fr 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 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 that= >>> 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. Thi= s >> 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 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). >> >> 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 importan= t >> to note that GStreamer and GNOME are moving over to using meson instea= d >> 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 pus= h >> this, I just got back from a break and I don't want to really deal wit= h >> 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 discussion= 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. --=20 Mathieu Arnold --99btd0QpQ3QbTKV5eB4gnRJx9X1mfLF7K-- --6BetvbhbJJtKVL9x7EQK9wxNh1K9HmfI4 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+TKhXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IUh8P/Rs2SBNgcZ6POD8eHnfyEt1m kr6QUiQxOuYrb/SHk9HsnuugNxZ1CPnWOUEc65GlcN0iMgWnmbW6QuRbsXL/A1Yu ZwY6HwxEaHOUzL9HZ/MA8e3xOtSmLbRVut4Jy9m5v5VnKBqZeCDkS1WRIo3MfJNd pCBjEHZPUtR7Do0OglD7k/jzVgQqROBZpnh7R5Hy4EFsoR+zM0hqch0hPxeKiBx9 vK3wm11XLwNeeP/5MrI5pR8eLCZxhqXD7+ZjXmE/zlNu0vAMDh6h1gERtVxRzXOL JAMHve0xAe4INH852gTyUMSqEkbE9yBe8bdkImcjQlJchms/lp7nGFJiVBSEgXmW iYUPff07+cANergO4eW2Dogb2t0iFbj6UDMcD/J9xl7BIP5cE0Bmcop7VPR64n6q oY21DJnO2hbXo+t3L97sAzuvn0F2l2nh6H53cLQ7/747nkECuSFXEsJ2o4F1DuUn XTxA9ZsebrIS5ZAFQeOX2KLQfCJJYALO7d9BMPcgyyv45CSHA4uYfCMm0rSdymfc 1h2xKy/h0zo8pU1l3h0srghnrNOjbu8ipJ49eN3lyPaMLm7CrDy6KbYOAGTH4J3E RNNws88dMrF1+psFqK7l6ixQ+5JjF1Nn2Ic6bH5o1PWUhEHY7qOZPSkkxLQyOKWO dHZE+kE52tpZGni/MVpS =9jJR -----END PGP SIGNATURE----- --6BetvbhbJJtKVL9x7EQK9wxNh1K9HmfI4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dee320db-98d5-177c-839f-68225e56a1ae>