public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: /etc/profile: avoid multiple /usr/bin in PATH
Date: Tue, 08 Dec 2015 21:01:00 -0000	[thread overview]
Message-ID: <87oae0venj.fsf@Rainer.invalid> (raw)
In-Reply-To: <op.x88uwyt9ofd6j1@frascati.upc.de> (Helmut Karlowski's message	of "Sun, 06 Dec 2015 23:47:12 +0100")

Helmut Karlowski writes:
> I set C:/cygwin/usr/bin in my windows-environment. Now /etc/profile
> always adds /usr/bin to PATH resulting in /usr/bin being twice in my
> cygwin-PATH.
>
> The attached patch fixes this.

I tend to reject this patch.  The purpose of the default profile is to
put those two paths in front, while with your patch they could end up
anywhere.  If you think that's OK for you, then you can already do that,
but I don't think that's a good default.

> It also sets SHELL if not yet set and avoids a call of hostname.

Can you tell me in which circumstances this happens and why this is a
problem?  SHELL is supposed to be the user preference, so I don't think
/etc/profile should try to second-guess it.

The second fork to hostname can indeed be removed.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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

  reply	other threads:[~2015-12-08 21:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 22:47 Helmut Karlowski
2015-12-08 21:01 ` Achim Gratz [this message]
2015-12-08 21:17   ` Helmut Karlowski
2015-12-08 21:21     ` Achim Gratz
2015-12-08 21:26       ` Helmut Karlowski
2015-12-08 21:31         ` Helmut Karlowski
2015-12-08 21:59           ` Helmut Karlowski
2016-09-04 11:32 ` Achim Gratz
2016-09-05  4:08   ` Doug Henderson
2016-09-05 17:57     ` Achim Gratz
2016-09-05 18:13       ` Vince Rice
2016-09-05 19:07         ` Achim Gratz

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=87oae0venj.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).