.so colophon.man

["Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>]

Hi Branden,

I'm wondering if it wouldn't be easier to have a constant '.so 
man-pages-colophon.man' line at the end of all of the Linux man-pages, 
instead of appending a COLOPHON at every release.  The 
man-pages-colophon.man file would be shiped together with the pages, and 
it would be created by `make dist`.

I think it's unnecessary to provide a dummy file in the repo, right?  I 
mean, .so is not like #include that would fail hard if the file doesn't 
exist.  It will instead just continue, right?

Do you think it would be a good idea?

I was making the COLOPHON be part of the `make dist` command (to avoid 
having to generate it separately), and this would simplify things a lot.
Not having to append to files controlled by make(1) would avoid having 
to rerun many recipes.

Cheers,

Alex

-- 
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/