Date: Sun, 13 May 2007 16:07:23 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: freebsd-hackers@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: DPS Initial Ideas Message-ID: <20070513200723.GA62750@xor.obsecurity.org> In-Reply-To: <464749FF.9090009@infracaninophile.co.uk> References: <20070512004209.GA12218@lpthe.jussieu.fr> <17989.8202.624522.136573@bhuda.mired.org> <20070512090935.GA13929@lpthe.jussieu.fr> <20070512193302.GA24673@xor.obsecurity.org> <20070512214422.GA88480@lpthe.jussieu.fr> <20070512222435.GA28981@xor.obsecurity.org> <4646C249.6070103@infracaninophile.co.uk> <20070513084404.GA35648@xor.obsecurity.org> <4646F084.3080601@infracaninophile.co.uk> <464749FF.9090009@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 13, 2007 at 06:25:19PM +0100, Matthew Seaman wrote:
> Matthew Seaman wrote:
>
> > Extra whitespace I can fix for you -- it's just the COMMENT field which
> > is affected IIRC. I just copy the string exactly as shown in the port's
> > Makefile. make index collapses multiple whitespace to single. As you say,
> > cosmetic. Also I get the sorting 'for free' by using the properties
> > of BDB btrees. Unfortunately it disagrees somewhat with the collation
> > order generated by sort.
>
> Here's the result of crunching multiple spaces in the COMMENT fields:
> This is after running the generated INDEX files through:
>
> cut -d '|' -f 1,4 INDEX
>
> Mostly it's the standard 'two spaces after a full stop', but there are a
> number of what look to me like mistakes. I can't parse that mosex entry
> at all..
COMMENT= Mozex allows users of ${GEKO} to use external programs for mail, news, etc.
It's supposed to be ${GECKO} I guess...it's another variant that will
change when the user (or a port) changes the value of that variable.
Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070513200723.GA62750>