Re: Allow configure variables to be set from environment

[Kristaps Dzonsons <kristaps@bsd.lv>]

Alexis,

Ingo's right on this one, but let's think a bit more.  There are a lot 
of OS X people out there and a lot of them use homebrew.  I think it's 
worthwhile to have (or at least consider having) an official mandoc in 
homebrew, but it should be done right.  Doing a naive installation isn't 
enough.

The problem, as mentioned, is that makewhatis(8) won't pick up any 
homebrew manuals, making mandoc(1) only useful as a standalone binary 
operating directly on manpages (e.g., mandoc path/to/manpage.1).

You can patch makewhatis(8) not to check if the manpage is looking at 
symlinks outside of the MANPATH, but that's effectively opening up a 
security hole where mandoc(1) tools might be run on basically anything. 
  (By the way, did you plan on cron'ing makewhatis(8) or anything?)

If you don't patch makewhatis(8) and install it as-is, you're going to 
confuse users when their manpages don't show up when using the other 
tools installed with the package (apropos, man, etc.) or when running 
the respective mandoc arguments (-a, -f, etc.).

So either you patch makewhatis(8) or patch the installation to *only* 
install mandoc, then patch mandoc to omit -f, -k, and -a, and not 
respond to being invoked as apropos, whatis, or man.

Essentially, the question is whether you want mandoc as a constellation 
of tools (a man replacement) with security tools or a developer tool.

I don't know what the correct solution is here.  Bref, homebrew has issues.

Best,

Kristaps
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv