Policy on new packages?

TheOldFellow theoldfellow at gmail.com
Tue Apr 1 13:42:48 PDT 2008

On Tue, 01 Apr 2008 14:31:57 -0500
Randy McMurchy <randy at linuxfromscratch.org> wrote:

> TheOldFellow wrote these words on 04/01/08 13:52 CST:
> > If I update to a2ps-4.14, we need gperf-3.0.3.  Is it policy to add it,
> > or just ref it directly to it's home page?
> It isn't written policy, but it would be nice. Especially for
> automated (not sure there is any) building of BLFS. If you have
> time great, if not, oh well.
> My build script for gperf shows CMMI, plus two additional commands:
> makeinfo -o doc/gperf.txt --plaintext doc/gperf.texi
> install -m644 -v doc/gperf.{dvi,ps,pdf,txt} /usr/share/doc/${PACKAGE_NAME}
> Not exactly sure because it is only creating a text file, but you may
> need TeX installed to create the doc.

OK, I'll add it preparatory to updating a2ps-4.14.  I still can't find
any reason to have the --localstatedir switch, so I'm going to drop
it.  The rest as detailed on the ticket.


More information about the blfs-dev mailing list