Re: install-mh location
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 script. Why? It's an obvious end-user program, especially now. It belongs in bindir. I doubt much if anything uses the old path (mh-e might, but note that it is still alive and kicking, arguably more so than nmh itself), so i say don't even bother with a backwards compatability symlink, but if you must have one the link goes in libexecdir. -- Eric Gillespie * [EMAIL PROTECTED] Build a fire for a man, and he'll be warm for a day. Set a man on fire, and he'll be warm for the rest of his life. -Terry Pratchett
Re: install-mh location
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 script. Why? It's an obvious end-user program, especially now. It belongs in bindir. I doubt much if anything uses the old path (mh-e might, but note that it is still alive and kicking, arguably more so than nmh itself), so i say don't even bother with a backwards compatability symlink, but if you must have one the link goes in libexecdir. -- Eric Gillespie * [EMAIL PROTECTED] Well, I already checked in a change to make it a link. Feel free to change it. By the way, should the manual page be changed from section 8 to section 1? Jon
Re: install-mh location
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 directory? Make a sym-link, or put in a shell script. Why? It's an obvious end-user program, especially now. It People have been using MH, and now nmh, for a very long time. They have come to expect things in particular places and my have local shell scripts that depend on it. with a backwards compatability symlink, but if you must have one the link goes in libexecdir. Putting the link in lib would be fine. -NWR
install-mh location
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; 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? Jon
Re: install-mh location
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, 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 script. -NWR
