Date: Thu, 25 Nov 2021 16:30:35 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: =?UTF-8?Q?Fernando_Apestegu=c3=ada?= <fernape@FreeBSD.org>, Ed Maste <emaste@FreeBSD.org>, src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-main@FreeBSD.org Subject: Re: git: 0a0f7486413c - main - man: Build manpages for all architectures Message-ID: <9226a616-d279-9702-f13f-cee7299afc7a@FreeBSD.org> In-Reply-To: <20211125142339.zxkjpbohkxk4hete@aniel.nours.eu> References: <202106300806.15U86pGq037942@gitrepo.freebsd.org> <20210706090311.aomxh4n45tkpktdc@aniel.nours.eu> <c272868f-8552-d914-9d63-32a4af8e51ce@FreeBSD.org> <20211125142339.zxkjpbohkxk4hete@aniel.nours.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25/11/2021 16:23, Baptiste Daroussin wrote: > On Thu, Nov 25, 2021 at 03:57:41PM +0200, Andriy Gapon wrote: >> Looking at the output I got another thought: do we need architecture sub-dir >> links at all now that we install manpages to a main directory? >> Is there any benefit to having the same manpage in a directory (like man4) >> and its immediate subdirectory (like man4/arm) ? >> > Hardlink not in the same directory is imho a fragile setup anyway, what if a > user has different mount points here, the hardlink would be broken. while there > is little chances someone is doing that, history told me people are doing weird > things and if they haven't yet, they will soon. > > I continue to think this kind of links should be 1/ symlinks, 2/ relative > symlinks if they are in a situation which can become a cross device issue. Yeah... but are they needed at all? :-) I mean, whichever way we install manpages they are always installed into manX. I do not see a point / benefit of having another copy / link / whatever in manX/arch. P.S. Adding support for "MSYMLINKS" is not that hard. But I'd rather remove some stuff than add some new stuff. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9226a616-d279-9702-f13f-cee7299afc7a>