From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 19955 invoked from network); 6 Sep 2021 15:52:55 -0000 Received: from bsd.lv (HELO mandoc.bsd.lv) (66.111.2.12) by inbox.vuxu.org with ESMTPUTF8; 6 Sep 2021 15:52:55 -0000 Received: from fantadrom.bsd.lv (localhost [127.0.0.1]) by mandoc.bsd.lv (OpenSMTPD) with ESMTP id 724de055 for ; Mon, 6 Sep 2021 10:52:52 -0500 (EST) Received: from mail1.systemli.org (mail1.systemli.org [212.103.72.247]) by mandoc.bsd.lv (OpenSMTPD) with ESMTP id 0b1bab4c for ; Mon, 6 Sep 2021 10:52:51 -0500 (EST) Message-ID: <6c8bb9c1-6d9e-b8f2-ba3f-7117c5fb8fe7@systemli.org> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=systemli.org; s=default; t=1630943569; bh=P4rvWnxCe/7eHVEk5ggngkAO/rNEwaqGxAUvgSJu0Sk=; h=Date:Subject:To:References:From:In-Reply-To:From; b=FRXAXnAhl46EEkh9U/qFovhx39jGZXEGsogqvaFkB5M65UO66hOmjo2AReStLJABR C8ug5t7NZZ8RBnD9SlD14sC01Uq+RdNhPUU6Sftf2yWOhCIXsCxZM9ObYj5uDfsF+U 2FyAXqkTKAXP0en17JoBxhHMl/0g/93ZMqfEB9Mk4Ho0Bu2TdChzwvkunBMPOVSUC8 OA3kGojr0zoY7Go1qXQ2gbiTgpwo794Q9UxUBJvYtIN5D1vU/5/BvPHUiLcB8JFqOq hLKUiYxeDZkOXpHMjAcMANiKQUY6bFVJu5yJKJxm27nAou2uyEGQGQKvKdzLDkHe6u MbV1pdEg3kQHA== Date: Mon, 6 Sep 2021 17:52:48 +0200 X-Mailinglist: mandoc-tech Reply-To: tech@mandoc.bsd.lv MIME-Version: 1.0 Subject: Re: makewhatis: segfault in dbadd when using -a Content-Language: en-US To: tech@mandoc.bsd.lv References: <20210811150959.GI38774@athene.usta.de> <14853b5f-c67e-a317-17fe-9c3a92f516b7@systemli.org> <20210819171150.GD56790@athene.usta.de> <20210906145047.GC83680@athene.usta.de> From: sternenseemann In-Reply-To: <20210906145047.GC83680@athene.usta.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Ingo, On 9/6/21 16:50, Ingo Schwarze wrote: > So, an acceptable way to support this probably exists, using the > FTS_FOLLOW option of the function fts_set(3). That isn't completely > trivial in this code which is already somewhat convoluted, but it > should not be excessively complicated either. That's good to hear! > Besides, i need to limit the difficulty of changes i'm doing right > now or i will never get the next release out of the door. So i > decided to postpone this particular feature until after release, > see the commit below. That's no problem and I agree that it should probably be prioritize in this way. It only affects a few, albeit annoying cases and there is a reasonable workaround for it. Also I'm still (as far as I can tell) the only user of mandoc's whatis db on NixOS since I haven't yet gotten around to upstreaming my module / been waiting for a release. Also one small clarification: > It doesn't matter that on first sight, this whole approach feels quite > fragile to me. Isn't that going to blow up in horrible ways as soon as > somebody creates a package that also uses "man3p"? For example, on > OpenBSD, "man3p" is used for manuals of Perl library functions. The symlink manpath is immutable in NixOS, so it will be recreated from scratch if the list of installed packages changes. Thus this is not an issue. Cheers, Lukas -- To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv