public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: How to handle length limit of PATH environment variable
Date: Thu, 05 Apr 2018 16:26:00 -0000	[thread overview]
Message-ID: <fee71278-1680-d1fd-6ffd-e958e6664ba8@SystematicSw.ab.ca> (raw)
In-Reply-To: <08077aa1-2da3-d381-8592-20c39acf063d@abacus.ch>

On 2018-04-05 04:05, Wolf Geldmacher wrote:
> On 05.04.2018 11:19, Peter Bauer wrote:
>> i was bitten by the length limit of the PATH variable of 4095 characters (see
>> [1]) and could not find a way around it. This means i have a lot of software
>> packages in different directories and each of them adds itself to the PATH so
>> one can run the executables and have the shared libs available. Under Windows
>> there is the "short path workaround" but what to do under Cygwin?
>> Creating links with shorter names to the directories is not feasible since
>> there may be different users and different directories per user.
>>
>> Any ideas?

> On Unix (though not on cygwin) I've previously solved such issues by writing a
> script that collects symlinks to the contents of some list of directories in a
> few (system and/or user specific) directories. These few directories then take
> the place of the list.
> 
> The script will need to be re-run whenever there are changes to the directories
> on the list, but that can usually be automated.

Under Cygwin, I ln -rs custom local Cygwin scripts and exes in:
	/usr/local/bin/
added at the head of the Cygwin PATH,
and to keep them separate from Cygwin components, put custom local Windows user
scripts and exes in:
	/proc/cygdrive/c/usr/local/bin/
added after all Cygwin dirs in PATH, before other Windows dirs.
I keep Windows system specific scripts e.g. .cmd, .reg and exes requiring
elevation in:
	/proc/cygdrive/c/usr/local/sbin/
separate from the unprivileged components.
I add /usr/local/bin/ to the head of the cron PATH, and /home/.../bin/ to the
tail of the cron PATH, so everything used in cron jobs is there; I run
everything in Scheduled tasks from C:\usr\local\bin\ for similar reasons.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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:[~2018-04-05 16:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05  9:19 Peter Bauer
2018-04-05 10:06 ` Wolf Geldmacher
2018-04-05 16:26   ` Brian Inglis [this message]
2018-04-05 11:50 ` Steven Penny
2018-04-05 17:50 ` Andrey Repin
2018-04-05 18:48   ` Achim Gratz
2018-04-06  0:35     ` Andrey Repin
2018-04-11 13:43     ` Peter Bauer
2018-04-06  0:31 ` Hans-Bernhard Bröker

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=fee71278-1680-d1fd-6ffd-e958e6664ba8@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).