From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp1.rz.uni-karlsruhe.de (Debian-exim@smtp1.rz.uni-karlsruhe.de [129.13.185.217]) by krisdoz.my.domain (8.14.3/8.14.3) with ESMTP id o9OI0LGE025985 for ; Sun, 24 Oct 2010 14:00:23 -0400 (EDT) Received: from hekate.usta.de (asta-nat.asta.uni-karlsruhe.de [172.22.63.82]) by smtp1.rz.uni-karlsruhe.de with esmtp (Exim 4.63 #1) id 1PA4rk-00006k-6f; Sun, 24 Oct 2010 20:00:20 +0200 Received: from donnerwolke.usta.de ([172.24.96.3]) by hekate.usta.de with esmtp (Exim 4.71) (envelope-from ) id 1PA4rk-0002LE-62 for tech@mdocml.bsd.lv; Sun, 24 Oct 2010 20:00:20 +0200 Received: from iris.usta.de ([172.24.96.5] helo=usta.de) by donnerwolke.usta.de with esmtp (Exim 4.69) (envelope-from ) id 1PA4rk-0003lO-51 for tech@mdocml.bsd.lv; Sun, 24 Oct 2010 20:00:20 +0200 Received: from schwarze by usta.de with local (Exim 4.71) (envelope-from ) id 1PA4rj-0000Az-MI for tech@mdocml.bsd.lv; Sun, 24 Oct 2010 20:00:19 +0200 Date: Sun, 24 Oct 2010 20:00:19 +0200 From: Ingo Schwarze To: tech@mdocml.bsd.lv Subject: Re: implement .so Message-ID: <20101024180019.GI20876@iris.usta.de> References: <20101024164057.GF20876@iris.usta.de> <20101024164945.GA25275@britannica.bec.de> <20101024172914.GH20876@iris.usta.de> <20101024173857.GA18657@britannica.bec.de> X-Mailinglist: mdocml-tech Reply-To: tech@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101024173857.GA18657@britannica.bec.de> User-Agent: Mutt/1.5.20 (2009-06-14) Hi Joerg, Joerg Sonnenberger wrote on Sun, Oct 24, 2010 at 07:38:57PM +0200: > On Sun, Oct 24, 2010 at 07:29:14PM +0200, Ingo Schwarze wrote: >> Converting .so to hard links would be an option if we were talking >> about just one build system. But ports have all kinds of different >> build systems. > Actually, if you consider ports itself as build system it is exactly > that. Once you have run the "make install" of the target package, > iterate over the PLIST of the package and check for .so usage in the man > pages and fix them up. That's similar to fixing up compressed vs > uncompressed man pages. That does indeed sound possible. But i doubt it causes less maintenance work compared to just implementing .so. * It would need to be done for both ports and Xenocara. * It would need to be done in each operating and ports system using mandoc; on a medium term, that may amount to at least four systems (OpenBSD, NetBSD, FreeBSD, DragonFly BSD). * From a maintenance perspective, .so does not seem that bad: it's strictly local in main.c without tentacles into any libs. * It would also put the code where it belongs: .so is a roff feature, not a build system feature. * All people i'm asking tend to say i should not worry that much about the my security concerns, maybe i'm indeed excessively paranoid in that respect. Yours, Ingo -- To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv