This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ANNOUNCEMENT] Updated: Cygwin 2.2.0-1


Am 07.08.2015 um 11:04 schrieb Corinna Vinschen:
Globally setting HOME in Windows for the sake of Cygwin was partially
necessary up to the early 2000s. For *at least* 12 years, it wasn't
anymore.
And people shouldn't be told to set HOME to a value not valid in the
environment they are setting it. Also considering that two applications were
mentioned that use it within Windows.
Finally, I think people shouldn't be told they cannot use the traditional
Unix feature (well-known to some) anymore because they should use some more
modern DB configuration method (system-specific, to be studied...).
So, editing /etc/passwd or /etc/nsswitch.conf is *that* hard?
Maybe not. But setting HOME is certainly easier. Especially if you're
not familiar with more specific, more modern configuration stuff, and
don't like to investigate first.
Also, there have been other valid reasons against a change; trying to
summarize:

 * Setting HOME would create a common home reference for multiple
   installations of cygwin (e.g. 32/64 bit) - strong reason.
 * Maintaining Unix tradition while accepting the syntax of the host
   system.
 * Windows software that also checks for HOME.
 * Finally, do you really want a bunch of complaints "my cygwin isn't
   finding my HOME anymore" without apparent benefit?

Thomas

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprÃft.
https://www.avast.com/antivirus


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]