On Wed, Jul 26, 2006 at 08:51:41AM -0400, Johnny Lam wrote:
> Joerg Sonnenberger wrote:
> >On Wed, Jul 26, 2006 at 10:14:59AM +0200, Gilles Dauphin wrote:
> >>
> >>>>Modified Files:
> >>>>	pkgsrc/net/tnftp: Makefile PLIST
> >>>>	pkgsrc/net/tnftp/files/src: Makefile.in
> >>>>
> >>>>Log Message:
> >>>>For consistency with the other tools from bootstrap, the preformatted
> >>>>manual page is installed as cat1/ftp.0 instead of cat1/ftp.1. Bumped
> >>>>PKGREVISION.
> >>>In fact, I'd prefer if no cat pages would be installed at all.
> >>>
> >>>Joerg
> >>I am not really OK with Joerg
> >>I'd prefer package with man pages correctly formated for targeted system.
> >
> >Yes, but duplicating the logic over packages is bad. As bad as wiering a
> >possible broken default value. Like I wrote in reply to rillig, this
> >should be handled as part of the post-install work if the platform/user
> >desires it, just like man page compression is already handled.
> 
> [NOTE: Moved to tech-pkg@NetBSD.org.  Please reply to that list.]

[this works better if the original list is just BCCed]

> This is fine for most packages, but I think the difference here is that 
> this is a potentially a bootstrap-installed package.  We may well want 
> to provide some formatted catman pages for just the bootstrap-installed 
> packages.

Are you talking about including cat pages (which it currently does and
which are formated for NetBSD) or building them as part of the package
build? Which brings up the much more interesting question: which
platforms have a problem with this magic?

I think we have three different situations here:
(a) Platforms which build catpages internally or don't use them at all.
DragonFly and FreeBSD belong into the former, Plan9 would fall into the
latter (no comments).
(b) Platforms which use catpages only and have the proper tools
installed already (troff/groff).
(c) Platforms which use catpages only and *don't* have the tools for
formating them.

For (a), we just should remove all created catpages on deinstall time.
For (b), post-install can run troff/groff with the platform default
settings even as part of the bootstrap.
Do we have examples for (c) and do we care strong enough about that?
Most of the tree won't work correctly for that in the current situation.

Joerg