From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: migrate a cygwin installation
Date: Sat, 01 Nov 2014 04:47:00 -0000 [thread overview]
Message-ID: <CAJ1FpuN-+M36OaHjR0Jq2e59R6K9+Y+J=64p=WUBXF5NUxqGqg@mail.gmail.com> (raw)
In-Reply-To: <m30gho$t2r$1@ger.gmane.org>
On 31 October 2014 11:23, Hans Horn wrote:
> What is the current recommended way to migrate a cygwin installation?
> my c: drive has gotten full to the brim.
> Tried to follow some older instructions online (~2009) but they do not seem
> to work anymore.
> Thx.
> H
You can use "cygcheck-dep -c -l -i" to list the minimum set of
packages required to reinstall all your installed packages. When you
run the architecture specific setup command, with the listed set of
packages selected, setup will recursively find all the packages
required by the selected packages. You will be prompted to accept a
list of these required packages after you click next from the package
selection screens.
On my laptop, I have 209 packages installed. The "cygcheck-dep -c -l
-i" command lists 46 packages. Some of these are included in the
initial package list, so they will be automatically installed on all
systems. If I manually select all the unselected members of this 46
package set, I will end up with 208 installed packages. The
cygwin-debuginfo will not automatically reinstall.
The <PKG>-debuginfo packages will not automatically reinstall, as they
are not automatically installed and do not have dependencies on other
packages. I would need to manually reinstall those, if I still needed
them. I do not have any <PKG>-src packages installed, so I am not sure
what will happen with those. Use the "cygcheck -c" command to get a
full list of your installed packages with version and status
information.
If you have test and prev package versions installed, this process
will install the current version. It does not attempt to handle
packages from other distributions like cygwinports and other "extra"
package sources.
I am currently using this process to semi-automatically generate a
batch file to quickly recreate a cygwin installation on new virtual
machines.
As always, YMMV.
Doug
--
Doug Henderson, 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
next prev parent reply other threads:[~2014-11-01 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 17:23 Hans Horn
2014-10-31 21:02 ` cyg Simple
2014-11-01 4:47 ` Doug Henderson [this message]
2014-11-01 10:35 ` Andrey Repin
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='CAJ1FpuN-+M36OaHjR0Jq2e59R6K9+Y+J=64p=WUBXF5NUxqGqg@mail.gmail.com' \
--to=djndnbvg@gmail.com \
--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).