Date: Sat, 05 Apr 2003 07:06:18 +0900 From: Kimura Fuyuki <fuyuki@hadaly.org> To: pfeifer@dbai.tuwien.ac.at Cc: ports@freebsd.org Subject: Re: MAN<x>-like support for .info files as well? Message-ID: <86of3llxyd.wl%fuyuki@hadaly.org> In-Reply-To: <Pine.BSF.4.53.0304041756080.88241@naos.dbai.tuwien.ac.at> References: <Pine.BSF.4.53.0304032136390.88500@naos.dbai.tuwien.ac.at> <86he9f9jwa.wl%fuyuki@hadaly.org> <Pine.BSF.4.53.0304041756080.88241@naos.dbai.tuwien.ac.at>
next in thread | previous in thread | raw e-mail | index | archive | help
At Fri, 4 Apr 2003 17:59:30 +0200 (CEST),
Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> wrote:
>
> On Fri, 4 Apr 2003, Kimura Fuyuki wrote:
> > Yes, indeed we need such a facility to deal with info files easily. But
> > how? I think it should allow us to specify at least the following
> > things:
> >
> > 1. a info file to pass install-info as an argument
> > 2. a wildcard(?) for split info files
>
> Based on my experience and given those those examples you provide, I would
> suggest to mainly consider the first two, at least for a first version.
>
> > * Template ("n" is number of the info, can be omitted. 2,3,4 are optional.)
> >
> > INFOn= 1 2
>
> This seems a very useful and easy-to-use approach, yes.
>
> Would it be sufficient to look for "1", that is, the base name of the info
> file(s), and have the $PORTSDIR/Mk machinery automatically check whether
> it is a single file or a series of files?
If it can be done, yes, I agree with you about the machinery
check. Perhaps we'd better start simple with the room for the further
expansion.
One problem: I don't also have enough skill to hack the tangly
bsd.port.mk. Gurus?
-- fuyuki
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86of3llxyd.wl%fuyuki>