X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=fut9yRBs0hFenJn6hGMTcd86mlMILxqgPw04LsGyru5vGWgt8i5Ev
	hMCF4THt79tatkhbI4RPcvvToQeVRZfbX5mcLqmcVJ9WuLvaAOfw+qstjXMkSvlf
	/0+WOLojn0J4tzX9aDj8s3hGxYT9UlD1zYPl7nbGux6ovNuiRvmuVQ=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=27MQSePAmScyhHpp1PbFs0mPCd8=; b=N1eRHvoAafmIGfDf9BF7kQxnWro6
	6hboet+om6HS6KtuEYKCmgqV7yyKLWCup4nuEle2V0zwaV8P7DTHyJGTY9zRaM6x
	dN5LC3h4bcj+z8mLd4EI5s+s00YtrYSijtJ3woG9pdNJfR1N2E0msJmxIzTkT47n
	io/msfId5FhbK0c=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status:	No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1+U4fg31ttUFSSJ3yMMoYZx
Date:	Thu, 27 Jun 2013 15:15:01 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: offline cygwin install question
Message-ID:	<20130627191501.GA5391@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<51CB4C14 DOT 4030909 AT molconn DOT com> <20130627083233 DOT GI6966 AT calimero DOT vinschen DOT de> <20130627165959 DOT GA7709 AT ednor DOT casa DOT cgf DOT cx> <51CC7BD4 DOT 6020208 AT molconn DOT com>
MIME-Version:	1.0
In-Reply-To:	<51CC7BD4.6020208@molconn.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)

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

- Raw text -