DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:to:subject:references
	:content-type; q=dns; s=default; b=mGUGe6nV8oJLK/MNo1l2zQeSc+ldw
	hKk2tq1D42Iy3+cRfgoBCZceJxO4VIVQsNZR/rjxZxhDBdQV4At2MZkl+/q3p2w5
	gTtLkpSXjUh4dAvuIioy4VGYosmmJ4gDpycK2wfuTm6bjqrFU9NF7TFRKijTLeQ+
	YeOOp8P2dxf7EI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <5ac60d72.d33ded0a.b9d4e.d0c4@mx.google.com>
Date: Thu, 05 Apr 2018 04:50:10 -0700 (PDT)
From: Steven Penny <svnpenn AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: How to handle length limit of PATH environment variable
References: <ebd804f3-8e24-d96f-7ef4-0e1279afd929 AT gmail DOT com>
Content-Type: text/plain; charset=utf8; format=flowed
User-Agent: Tryst/2.4.0 (github.com/svnpenn/tryst)

On Thu, 5 Apr 2018 11:19:01, 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.

My Cygwin PATH looks like this:

    PATH=/usr/local/bin:/usr/bin

However I also have an install script that has lines like this:

    ln -s 'c:/program files/gpac/mp4box.exe' /usr/local/bin

This is good because you often *dont* want to be adding these directories to the
PATH. Good example is "C:\Windows\System32". It might have some programs you
want on the PATH (FTP, PING, REG, SETX), but if you add the whole directory you
are going to get collisions (EXPAND, FC, FIND, HELP, RESET, etc)


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