public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.2.0-1
Date: Fri, 07 Aug 2015 22:19:00 -0000	[thread overview]
Message-ID: <55C52EF5.5060009@towo.net> (raw)
In-Reply-To: <20150807090443.GA12475@calimero.vinschen.de>

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

  parent reply	other threads:[~2015-08-07 22:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 13:28 Corinna Vinschen
2015-08-03 18:43 ` Thomas Wolff
2015-08-03 19:29   ` Corinna Vinschen
2015-08-04  7:51     ` Achim Gratz
2015-08-04 18:14       ` Warren Young
2015-08-04 18:44         ` Thomas Wolff
2015-08-04 18:53         ` Achim Gratz
2015-08-05  7:54           ` Corinna Vinschen
2015-08-05  9:09             ` Thomas Wolff
2015-08-05 10:12               ` Corinna Vinschen
2015-08-06 12:03                 ` Thomas Wolff
2015-08-07  9:04                   ` Corinna Vinschen
2015-08-07 15:27                     ` cyg Simple
2015-08-07 22:19                     ` Thomas Wolff [this message]
2015-08-05  9:19             ` Kiehl, Horst
2015-08-05 10:09               ` Corinna Vinschen
2015-08-05 16:50               ` Andrey Repin
2015-08-05 16:50             ` Andrey Repin
2015-08-05 23:58               ` Nicholas Clark
2015-08-06  0:20                 ` Andrey Repin
2015-08-06  0:35                   ` Nicholas Clark
2015-08-06 11:35                     ` Andrey Repin
2015-08-07 15:16             ` cyg Simple

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55C52EF5.5060009@towo.net \
    --to=towo@towo.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).