Date: Fri, 3 Jun 2005 14:22:05 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Matthias Andree <matthias.andree@uni-dortmund.de> Cc: "Loren M. Lang" <lorenl@alzatex.com>, freebsd-ports@freebsd.org Subject: Re: Man pages compressed with bzip2 Message-ID: <20050603182205.GA49376@xor.obsecurity.org> In-Reply-To: <42A04F40.7000906@uni-dortmund.de> References: <20050602225624.GB24057@alzatex.com> <42A04F40.7000906@uni-dortmund.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 03, 2005 at 02:38:24PM +0200, Matthias Andree wrote: > Loren M. Lang wrote: > > An application I am porting comes with it's manpages already formatted > > and compressed with bzip2, though freebsd doesn't support bz2 manpages, > > AFAIK. But if it does, I don't think the ports framework can handle it > > as there doesn't seem to be anyway to specify the compression format for > > manpages. What is the best solution to this? > >=20 > > Should I just write a post-build target that will decompress it and > > recompress it as gz >=20 > I'd do just that: recompress. gzip decompresses much faster, so .bz2 man > pages may become an annoyance on slower machines. Yes. > > and just add bzip2 as a dependency or should I just >=20 > A build dependency. I don't think this is necessary, because all supported versions of FreeBSD contain bzip. Kris --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCoJ/MWry0BWjoQKURAmpUAJoCnTjJGjGGEjWT9dRbOt4EHTgPIgCgiASB KhPiHNbgV0C/H07MCnjjVrM= =ZpG4 -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050603182205.GA49376>