public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: Bill Stewart <bstewart@iname.com>, cygwin@cygwin.com
Subject: Re: Capturing a Cygwin instance from another PC
Date: Wed, 22 Nov 2023 11:15:17 -0500	[thread overview]
Message-ID: <147f983f-eab8-4605-11e6-14709c56d87b@cs.umass.edu> (raw)
In-Reply-To: <CANV9t=QVXeT+rBuSuZu4ogic36L4SRUqqAerCyAYzvKKqm+iUQ@mail.gmail.com>

On 11/22/2023 10:43 AM, Bill Stewart via Cygwin wrote:
> On Wed, Nov 22, 2023 at 7:53 AM Jose Isaias Cabrera wrote:
> 
> I have a new Win11 PC, and I wanted to capture the same Cygwin setup that I
>> have in another Win10 PC. I copied the C:\cygwin64 folder from the Win10 pc
>> to the Win11 pc, then I downloaded a fresh setup-x86_64.exe from
>> cygwin.com to the win11 PC. I ran it and chose "Install from Local
>> Directory" and only one shortcut for "Cygwin64 Terminal" was created on the
>> desktop. No Cygwin nor Cygwin-X folders were created on the Start menu. The
>> original cygwin from the Win10 PC had X installed also.
>>
> 
> I don't think "Install from Local Directory" means "reproduce same cygwin
> installation on a separate computer".

In fact, it means to install using the package files in some local directory,
i.e., "assume the packages are already downloaded".

It would be reasonable to copy over downloaded packages.

I believe there are commands / techniques that would then make it fairly
easy to install that specific set of packages "from scratch" (but from
the local copy of the packages).  Copying *installed* file hierarchies
is trickier because of permission / ownership concerns.

Best - EM

  reply	other threads:[~2023-11-22 16:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 14:53 Jose Isaias Cabrera
2023-11-22 15:43 ` Bill Stewart
2023-11-22 16:15   ` Eliot Moss [this message]
2023-11-22 21:38     ` Jose Isaias Cabrera
2023-11-22 22:01       ` Ken Brown
2023-11-23  3:25       ` Eliot Moss
2023-11-23  9:12         ` Backwoods BC
2023-11-22 22:44     ` Cedric Blancher
2023-11-23 15:24       ` Corinna Vinschen
2023-11-22 16:20 ` EXTERNAL SENDER: " Dale Lobb (Sys Admin)
2023-11-22 21:49   ` Jose Isaias Cabrera
2023-11-23 18:40 ` ASSI
2023-11-23 20:27   ` Doug Henderson
2023-11-27  2:36 ` Chris Wagner
2023-11-27  8:24   ` ASSI
2023-11-27 17:43     ` Brian Inglis
2023-11-29 17:42       ` Jose Isaias Cabrera
2024-01-14 19:23       ` Andrey Repin
2023-11-27  2:46 ` Capturing a Cygwin instance from another PC (CORRECTION) Chris Wagner
2023-12-07 22:59 ` Capturing a Cygwin instance from another PC Andrew Schulman

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=147f983f-eab8-4605-11e6-14709c56d87b@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=bstewart@iname.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).