On 6/23/2023 10:35 PM, Brian Inglis wrote:
On 2023-06-23 20:19, Dan Harkless via Cygwin wrote:
> Before you resort to trawling through source, did you try a fresh Cygwin install
> (either to a different directory, or after temporarily moving your current
> tree)? Sometimes, e.g. if you use the same "packages" directory between two
> different versions of Windows, I've found that Cygwin can get screwed up in
> strange ways.
The -l|--local-package-dir DIR Local package directory just saves the downloaded
tar file in case you want to do a reinstallation.
I would expect trying to share the same -R|--root DIR Root installation
directory between different systems, when you can really only install on one,
and each host system requires specific unique keys to be generated, could give
you questionable setups.
No, I'm not talking about sharing the same install tree between major
versions of Windows, just the downloaded "packages" directory. I
realize it's just supposed to be a download cache, but I promise I've
had mysterious failures that were only resolved by using a separate
packages dir for each multi-boot OS. It's possible this only occurred
in the past due to setup[...].exe bugs which have since been fixed, but
Chris' mysterious ssh issue (and his mention of upgrading from a much
older Cygwin version, and using both Windows 10 and Windows 11) reminded
me of the strange things I used to sometimes experience before I stopped
sharing the packages directory across OSes.
--
Dan Harkless
http://harkless.org/dan/
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
