From: Eliot Moss <moss@cs.umass.edu>
To: Jose Isaias Cabrera <jicman@outlook.com>,
Bill Stewart <bstewart@iname.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Capturing a Cygwin instance from another PC
Date: Wed, 22 Nov 2023 22:25:58 -0500 [thread overview]
Message-ID: <8e38b937-1a61-fbf7-4b72-9a836d6d3520@cs.umass.edu> (raw)
In-Reply-To: <DB9P251MB0063AA52CFACD26EA07C4DC5DEBAA@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM>
On 11/22/2023 4:38 PM, Jose Isaias Cabrera wrote:
> On Wednesday, November 22, 2023 11:15 AM, Eliot Moss expressed:
>>
>> 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:
> [clip]
>> >> 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.
>
> Thanks, Eliot. Hmmm... I would have thought that by now this process would have been thought of.
Not saying it hasn't, but since I don't have a ready answer to your
question I was leaving that to other, more knowledgeable, folks to
jump in and ill the gap :-) ...
EM
next prev parent reply other threads:[~2023-11-23 8:38 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
2023-11-22 21:38 ` Jose Isaias Cabrera
2023-11-22 22:01 ` Ken Brown
2023-11-23 3:25 ` Eliot Moss [this message]
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=8e38b937-1a61-fbf7-4b72-9a836d6d3520@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=bstewart@iname.com \
--cc=cygwin@cygwin.com \
--cc=jicman@outlook.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).