This is the mail archive of the cygwin-developers 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] |
On 6/28/11 12:51 PM, Charles Wilson wrote: > Right, we have to decide -- my point is there isn't an easy answer that > will have zero impact on everybody. There are basically three choices: > > /bin + /bin64 -- affects $PATH, implicates package naming (*). Also > might affect script #! lines, and anything that calls > exec*() or spawn() with a full pathname. So if I have a foo-32bit.exe in a directory that's not /bin or /bin64, it might segfault on startup depending on whether /bin or /bin64 comes first in $PATH? And whichever path is correct for foo-32bit.exe will be incorrect for foo-64bit.exe and vice versa?
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |