From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: offline cygwin install question
Date: Thu, 27 Jun 2013 19:22:00 -0000 [thread overview]
Message-ID: <20130627191501.GA5391@ednor.casa.cgf.cx> (raw)
In-Reply-To: <51CC7BD4.6020208@molconn.com>
On Thu, Jun 27, 2013 at 01:52:20PM -0400, LMH wrote:
>I have win7 64-bit computers set up in another location. It would seem
>that the easiest option would be to make sure that one of those is up to
>date and then just tar up the cygwin directory and move it.
http://cygwin.com/ml/cygwin/2013-06/msg00657.html
>I have also
>found that you can just tar up the local package directory and then run
>a local install, but this seems to have issues if there are packages in
>the local install dir from more than one mirror.
I don't see why. If the directory is duplicated precisely I don't see
how it could matter.
>If I download the normal setup.exe to a 64-bit windows install, will it
>automatically install the 64-bit version?
No.
>I have never seen the setup64.exe that was mentioned in a previous
>post. Where would that be located?
64-bit Cygwin is currently still in beta. setup64 is in the '64bit'
directory on any mirror. You can't use it to change a Cygwin
installation from 32 - 64 bit though.
cgf
--
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:[~2013-06-27 19:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 2:35 LMH
2013-06-27 2:40 ` wynfield
2013-06-27 4:49 ` LMH
2013-06-27 8:32 ` Christopher Faylor
2013-06-27 13:08 ` Buchbinder, Barry (NIH/NIAID) [E]
2013-06-27 8:33 ` Corinna Vinschen
2013-06-27 17:00 ` Christopher Faylor
2013-06-27 18:25 ` LMH
2013-06-27 19:22 ` Christopher Faylor [this message]
2013-06-27 20:19 ` LMH
2013-06-27 20:47 ` Christopher Faylor
2013-06-28 22:05 ` Christopher Faylor
2013-09-08 5:40 R.Penney
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=20130627191501.GA5391@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@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).