From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Replicate packages from 32-bit machine on 64-bit machine
Date: Fri, 22 Aug 2014 19:01:00 -0000 [thread overview]
Message-ID: <53F7937B.5040404@cygwin.com> (raw)
In-Reply-To: <loom.20140822T201659-254@post.gmane.org>
On 08/22/2014 02:17 PM, Paul.Domaskis wrote:
> Larry Hall (Cygwin <reply-to-list-only-lh <at> cygwin.com> writes:
>> On 08/18/2014 10:30 AM, Paul wrote:
>>> Andrey Repin <anrdaemon <at> yandex.ru> writes:
>>>> When I wanted to replicate my cygwin installation from a 32-bit
>>>> machine to another 32-bit machine, it was straightforward. I would
>>>> simply reinstall all installed packages, but have the downloaded
>>>> packages got to a folder which I then burn to CD.
>>>>
>>>> However, my next machine is a 64-bit machine. So I have to use the
>>>> 64-bit setup. Is there an almost-as-painless way to replicate the
>>>> 64-bit version of the packages that I have installed on my 32-bit
>>>> machine?
>>>
>>> You contradicting yourself. 64-bit packages are entirely different
>>> files than 32-bit packages.
>> Yes, I understand. I was referring to the 64-bit versions of my
>> 32-bit packages. It took quite some period of discovery to determine
>> my operational needs and the packages required. I'm hoping to avoid
>> that re-experiencing that.
>>
>> You shouldn't have allot of trouble matching the 64-bit version of any
>> package with the 32-bit version. Assuming there is a 64-bit version of
>> the package you want, package names are typically very similar between
>> the two architectures.
>
> Understood, Larry. It's just that there are so many packages, and I
> don't want to manually find all the matching packages. Before, if I
> wanted to replicate a cygwin install on another machine, I just
> reinstalled all my packages, but saved the packages to a folder that I
> could write to disc. I can't do that if I want to replicate my
> packages as 62-bit versions.
Well, right. There's no way to automatically map all 32-bit packages
to their 64-bit counterparts, particularly because there isn't always a
64-bit package to map to. What I was suggesting was a method you could
use to make a first pass at the 64-bit packages that you want to download.
It won't be perfect but it would be a quicker alternative to doing this
all manually. But if 64-bit packages are what you're looking for, you
definitely have to go through some process for this once. After that,
you can employ the same technique to replicate your 64-bit installation
elsewhere.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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-08-22 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 6:41 paul
2014-08-17 12:01 ` Eliot Moss
2014-08-18 14:05 ` Paul
2014-08-18 0:35 ` Andrey Repin
2014-08-18 14:31 ` Paul
2014-08-18 14:58 ` Larry Hall (Cygwin)
2014-08-22 18:18 ` Paul.Domaskis
2014-08-22 19:01 ` Larry Hall (Cygwin) [this message]
2014-08-22 22:10 ` Adam Dinwoodie
2014-09-05 15:41 ` Paul
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=53F7937B.5040404@cygwin.com \
--to=reply-to-list-only-lh@cygwin.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).