Jon Steinhart <[EMAIL PROTECTED]> writes:
> By the way, should the manual page be changed from section 8 to section 1?
Holy crap, yes. Even when it was in libexecdir the man page did
not belong in section 8.
--
Eric Gillespie <*> [EMAIL PROTECTED]
Build a fire for a man, and he'll be warm fo
Eric Gillespie <[EMAIL PROTECTED]> wrote:
>Neil W Rickert <[EMAIL PROTECTED]> writes:
>> >But, install-mh is not likely to be in the user's path;
>> >it's in the lib directory. Should I change the
>> >installation to move this to the bin directory or to
>> >make a link from the bin to the lib dir
> Neil W Rickert <[EMAIL PROTECTED]> writes:
>
> > >But, install-mh is not likely to be in the user's path;
> > >it's in the lib directory. Should I change the
> > >installation to move this to the bin directory or to
> > >make a link from the bin to the lib directory?
> >
> > Make a sym-link, o
Neil W Rickert <[EMAIL PROTECTED]> writes:
> >But, install-mh is not likely to be in the user's path;
> >it's in the lib directory. Should I change the
> >installation to move this to the bin directory or to
> >make a link from the bin to the lib directory?
>
> Make a sym-link, or put in a shell
Jon Steinhart <[EMAIL PROTECTED]> wrote:
>Well, here's a minor detail that could cause problems.
>I have a version of nmh here that has sbr/context_read
>modified to give a "run install-mh" message if mh
>isn't installed rather than doing it for the user as
>per yesterday's discussion.
>But, inst
Well, here's a minor detail that could cause problems.
I have a version of nmh here that has sbr/context_read
modified to give a "run install-mh" message if mh
isn't installed rather than doing it for the user as
per yesterday's discussion.
But, install-mh is not likely to be in the user's path;
i
