On Tue, 2008-05-27 at 12:09 +0200, Bernd Jendrissek wrote: > On Mon, May 26, 2008 at 9:29 PM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > * Bernd Jendrissek wrote on Thu, May 08, 2008 at 09:41:36PM CEST: > >> On Wed, May 7, 2008 at 1:07 PM, John Darrington <[EMAIL PROTECTED]> wrote: > >> > How can I change it so that compressed versions are installed instead? > >> > >> Same for man pages. Back when I kept a private set of build scripts > >> for half a zillion packages, I had an m4 macro that expanded to a > >> shell command that would compress these resources, after 'make > >> install' had finished. It was a bit fragile with TEXINFOS though, > >> since the info files didn't all have the same filename extension. (I > >> recall having some fun with info itself, as it would install it's > >> documentation named info.info. My naive filename glob broke on that.)
I am strongly opposed to adding such feature to automake, because man-page compression is a target system's and a system-integrator feature, not a package feature. So, if at all, enabling such feature should remain strictly optional and must remain configurable by the system integrator - To me, this doesn't make much sense. > > Not all system's man programs cope with compressed manpages. I know > > some (most? all?) GNU/Linux distributions install compressed manpages, Some GNU/Linux distros install *bz2'ed manpages, other might be using something completely different in future, ... > > I assume it's rpm/deb/... features that compress them, right? > > I assume so too. Correct, as far as rpm is concerned. Rpm implicitly compresses them as part of building a package by running some scripts. Ralf
