Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-Id: <199911192247.QAA07188@mercury.xraylith.wisc.edu> To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: cygwin PATH reorg? In-Reply-To: Your message of "Fri, 19 Nov 1999 12:20:47 PST." <19991119122047 DOT B32163 AT cygnus DOT com> Date: Fri, 19 Nov 1999 16:47:15 -0600 From: Mumit Khan Geoffrey Noer writes: > > This doesn't sound like a good idea to me. Somewhat hidden cleverness > is really dangerous. Could better documentation possibly accomplish > the same goals? Dunno, but I would think that would be preferable. > I'm not sure what you mean adding /bin to the PATH automagically. I, as a user, don't care as long as my PATH does not change after the shell evaluates my startup files (.profile, etc). If you can add /bin as the first element to the PATH variable before it gets to my startup file, it sounds like a good idea. I'm in favor of the Unix'y login approach -- setup a default bare environment, and then let the actual user startup take care of the rest. This bare environment setup process can put /bin, however it is found, before the rest of the User's existing PATH (done via Windows/DOS); then .bashrc/.profile does the rest. I'd think /bin should be easy to find. Have the installer add a registry entry that says where it was installed (it's already there in a way), and use that to find /bin. Regards, Mumit