From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Is there a way to clone-install Cygwin?
Date: Tue, 21 Jan 2020 20:33:00 -0000 [thread overview]
Message-ID: <87y2u0a6tv.fsf@Rainer.invalid> (raw)
In-Reply-To: <SN6PR09MB2877F202738BF6B7029538F3A50D0@SN6PR09MB2877.namprd09.prod.outlook.com> (Anton C. via cygwin Lavrentiev's message of "Tue, 21 Jan 2020 00:58:39 +0000")
Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin writes:
> I have a question, is there a way to clone-install Cygwin?
Multiple, but if you like to do it without any extra tools you'll have
to cheat a little.
> Like I have installed whatever packages I selected on some PC, then
> maintained that installation for a while, doing upgrades etc. Now I
> need to install the exact same set on another PC. Can I pull up a
> list and use it in a sort of a batch install with setup.exe? I want
> to avoid to dumb-copy the entire C:\cygwin tree from one PC to
> another, rather use a semi-automatic install procedure from scratch,
> if possible, using the list of packages that I need.
One way to do that is to take /etc/setup/installed.db from the old
system an drop it to the same place in the new system, then run
setup.exe and "reinstall" all packages. You'll have to re-do all
customization steps that wereN#t done as part of the installation
itself, but you seem to know that already.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
--
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:[~2020-01-21 20:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 0:58 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-21 1:27 ` Brent Epp
2020-01-31 10:25 ` Ulli Horlacher
2020-01-31 11:29 ` Ulli Horlacher
2020-01-31 12:05 ` Ulli Horlacher
2020-01-31 12:54 ` Thomas Wolff
2020-01-31 14:06 ` Ulli Horlacher
2020-02-01 10:05 ` Andrey Repin
2020-02-01 11:21 ` BGINFO4X
2020-02-03 16:40 ` Ulli Horlacher
2020-02-03 17:01 ` BGINFO4X
2020-02-04 17:16 ` Ulli Horlacher
[not found] ` <16fc5b08e80.2780.a1382e26d1292f71ec6ef0cd03d49346@pdc.ca>
2020-01-21 2:33 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-21 2:55 ` Brent Epp
2020-01-21 4:46 ` Marco Atzeri
2020-01-21 20:33 ` Achim Gratz [this message]
2020-01-28 21:35 ` Andrey Repin
2020-01-28 22:00 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-21 19:17 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-31 14:06 KARL BOTTS
2020-01-31 14:13 ` Ulli Horlacher
2020-01-31 19:21 ` Achim Gratz
2020-01-31 20:25 ` Brian Inglis
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=87y2u0a6tv.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).