[Pm-utils] [PATCH 1/1] Do not track the man pages.

Victor Lowther victor.lowther at gmail.com
Sat Mar 8 08:07:48 PST 2008


On Sat, Mar 08, 2008 at 09:17:49AM +0100, Michael Biebl wrote:
> 2008/3/8, Dan Nicholson <dbn.lists at gmail.com>:
> > On Fri, Mar 7, 2008 at 2:20 AM, Michael Biebl <mbiebl at gmail.com> wrote:
> >  >
> >  >  Shouldn't we add a configure check for docbook2man then? On the other
> >  >  hand, as we distribute the man pages in the dist tarball, docbook2man
> >  >  is not strictly necessary either.
> >
> >
> > Yes, but I don't have docbook2man everywhere. The Makefile should be
> >  conditional on whether I have it so I don't bomb my build on the man
> >  pages. Something like:
> >
> >  configure.ac
> >  ...
> >  AC_PATH_PROG(DOCBOOK2MAN, docbook2man, no)
> >  AM_CONDITIONAL(HAVE_DB2MAN, test "x$DOCBOOK2MAN" != xno)
> >  ...
> >
> >  and then surround the man_MANS in Makefile.am with "if HAVE_DB2MAN".
> >
> 
> The problem with that is, that the one, creating the official dist
> tarballs, could miss to include the man pages.
> 
> With the current solution, only developers using the git clone, will
> have to have docbook2man installed. Users who download the final
> tarballs don't.
> I think that's a fair compromise.

AOL.

I just wanted to stop tracking the man pages in the gitrepo because they
are autogenerated.

The official dist tarballs should definitly include the man pages, and
the make process should die horribly if it can't create the manpages
when making a dist tarball.
 
> Cheers,
> Michael
> 
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?

-- 
Victor Lowther
Ubuntu Certified Professional


More information about the Pm-utils mailing list