Nice saturday,
Peter Schaffter <pe...@schaffter.ca> wrote:
|On Fri, Mar 14, 2014, Steffen Nurpmeso wrote:
|> well ok, i think i have something that i could post (after some
|> more checking, i.e., tomorrow).
|> What would you say about an additional --with-examples?
|
|What would be the point? PREFIX/doc/examples occupies
|over 3/4 of PREFIX/doc. What gain would there be in
|'--without-doc --with-examples', other than bypassing
|the netpbm dependency? Might as well install netpbm
|(recommended in README) and build the whole shebang.
It thought more about --without-examples solely, but i haven't yet
looked if that is possible at all. (Consciously never used
autotools.)
|> And how fully blown do you actually want it: should a `make dist'
|> fail and complain if documentation (plus) is not complete, or is
|> it ok to simply assume someone who runs `make dist' knows about
|> the make system?
|
|Can't imagine a situation where 'make dist' would want to exclude
|documentation. Assume nothing. :)
It's no joke, it's not only me who is sometimes sloppy
(hyperactive is i hope/think more correct) -- just recently
a (rather widespread) program release shipped with forgotten
object files etc. I like safety-belts like that. There exist
personalities which would never fail when doing such tasks.
(Unfortunately those in the atomic bomb launch sites are not of
that kind, if you trust that study i have in mind.)
|For consistency with other configure options,
|
| --with-doc[=ARG] [ARG=yes]
| --without-doc (same as --with-doc=no)
|
|is probably best.
Hm, i currently have
--with-doc[=TYPE] choose which manuals (beside man pages) are
desirable. Give TYPE as a comma-separated list of
one or multiple of `info', `pdf' and `html' to
restrict what is produced
being a superset of what you say.
How about adding `examples' to this list?
I'll do that and post it -- if you don't like it cutting that
down again is a matter of minutes.
--steffen
