From: Andrey Repin <anrdaemon@yandex.ru>
To: Jim Reisert AD1C <jjreisert@alum.mit.edu>, cygwin@cygwin.com
Subject: Re: Can I rename my C:\Cygwin64 directory to C:\Cygwin?
Date: Thu, 17 Nov 2022 21:24:05 +0300 [thread overview]
Message-ID: <3910073505.20221117212405@yandex.ru> (raw)
In-Reply-To: <CAK-n8j45a=Nqy-AKR9sk0c479Uo=-nYiNbMWQz9tSuz_WmhRwg@mail.gmail.com>
Greetings, Jim Reisert AD1C!
> Now that Cygwin x86 is nearing/has reached end-of-life, I would like
> to rename my C:\Cygwin64 directory to C:\Cygwin.
> Other than updating my Windows environment variable (CYGROOT), are
> there any "gotchas" in doing this? I already have a D:\Home directory
> specified in /etc/nsswitch.conf so I'm not expecting the move to break
> that.
Please look for my earlier message[1](thread) regarding installation path
changes for provided PowerShell script.
> Where does setup.exe get its information from? Is there a .ini file
> that I will need to edit?
Whoever it gets the information, you could easily change it the first time you
update the installation at the new place.
Consider it a non-issue.
The rest of the information is taken from `$InstallPath/etc/setup`
> My main concern is that the Cygwin Perl installer may get confused. I
> currently have this in my Cygwin environment. It doesn't appear that
> such a change will be a problem:
>
> PERL5LIB=/cygdrive/d/Home/perl5/lib/perl5:/cygdrive/d/Home/perl5/lib/perl5:/cygdrive/d/Home/perl5/lib/perl5
> Is there anything else I'm missing?
Depends on your setup, existing symlink targets may be a problem.
[1] https://cygwin.com/pipermail/cygwin/2022-August/thread.html#252113
--
With best regards,
Andrey Repin
Thursday, November 17, 2022 21:18:24
Sorry for my terrible english...
next prev parent reply other threads:[~2022-11-17 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 16:58 Jim Reisert AD1C
2022-11-17 18:24 ` Andrey Repin [this message]
2022-11-17 22:57 ` Jim Reisert AD1C
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=3910073505.20221117212405@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=jjreisert@alum.mit.edu \
/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).