>> but I still get the error, and if I just want the ctwm executable
>> I'm not sure why my manpath matters anyway. E.g.,
> In concept, I guess we could wait until the manpage install process to
> throw the error.
Yes, yes, yes, please.
I can't remember ever "make install"ing ctwm, even though I've been
using my own build (regularly hacked and updated) for the last 20 years.
> I always feel better about dying as soon as
> something's known bad though;
But throwing an error about something that the user might do some time
in the future is confusing. If you throw the error during "make
install", it's pretty obvious to the user that "make" is having trouble
deciding where to install the manpages. If you throw the error during
"make", I (as a user) start wondering "what could manpath have to do
with it? Does it need to find some man page to decide which
compilation switch to use, or what?", so it won't occur to me to pass
the "destination manpath" but instead I'll try to provide some of the
system's manpath (to which I probably don't have write access).
> it feels unfriendly to go all through the build, install ctwm and its
> files, and THEN "Oops" trying to install the manpage, leaving you with
> a partial install.
I can agree that the error should be signaled before starting to install
other files (tho I don't think it'd be so terrible), but that doesn't
justify signaling an error for a command that won't install any file at all.
Stefan
