public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: tar cygwin64/ from old to new computer?
Date: Sun, 25 Nov 2018 17:20:00 -0000	[thread overview]
Message-ID: <87y39hkrb7.fsf@Rainer.invalid> (raw)
In-Reply-To: <20181125143854.GA20164@ingber.com> (Lester Ingber's message of	"Sun, 25 Nov 2018 06:38:54 -0800")

Lester Ingber writes:
> I'd like to simply transfer my cygwin64/ directory from my old Thinkpad
> to my new Thinkpad, both running Win 10 x64 Pro.  E.g., I would put my
> old c:/cygwin64/ onto a flash SSD USB drive e:/ .
> cd c:/
> tar cfp - cygwin64 > e:/cygwin64.tar &
> Then e:/cygwin64.tar would be mounted on my new computer.

That may or may not work, but please don't (especially not if there's a
chance that the old Thinkpad will be used in parallel to the new one).
What you do want to keep is any files you have added/edited, but you'll
have to check if these edits are still valid.

> I'm assuming that there is not actual install required, e.g., having to
> run setup-x86_64.exe first on the new computer?

The thing you can do is drop the install.db file from the old computer
to where it would be in the new (before or after a Base install),
nulling all the version strings (I've posted an example of how to do
that on this list some time ago).  Then setup.exe will find and
"upgrade" for all those packages you've had installed previously.
However, it may not be the worst idea to drop packages that you don't
actually use anymore, so a fresh install may not be a bad idea.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

--
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

  parent reply	other threads:[~2018-11-25 17:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25 14:39 Lester Ingber
2018-11-25 17:09 ` Hans-Bernhard Bröker
2018-11-25 19:22   ` tar cygwin64/ from old to new computer: L A Walsh
2018-11-25 20:05     ` Andrey Repin
2018-11-26 19:19       ` L A Walsh
2018-11-25 17:20 ` Achim Gratz [this message]
2018-11-25 18:50 ` tar cygwin64/ from old to new computer? Andrey Repin
2018-11-25 19:31 ` Lester Ingber
2018-11-25 20:13   ` Achim Gratz
2018-11-26 13:47     ` KARL BOTTS
2018-11-26 20:32 Gilbert St. Firmin
2018-11-26 21:22 ` Hans-Bernhard Bröker
2018-11-27 15:20 ` Andrey Repin
2018-11-27 15:34   ` cyg Simple

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=87y39hkrb7.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).