DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:content-type
	:content-transfer-encoding:mime-version; q=dns; s=default; b=E0N
	/gxshaSIULz1XEX08qh2013x3mpZdD/bhAizvARR9pP0Xt3jpOMJcSMXr74Lp3sQ
	2ddf3vynLfo60D5Cejmk9ADebSEDAWZZJuwD2glkg6EbLY5E+nrxbWkaoO4dqjgU
	Fd054qtryv4puXO1boVg0Qo/zPJsV3aFxiYb65YY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Nellis, Kenneth" <Kenneth.Nellis@xerox.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: 32-bit/64-bit sharing of Local Package Directories
Date: Mon, 17 Nov 2014 14:39:20 +0000
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A702E8442CA@USA7109MB022.na.xerox.net>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

I currently maintain separate 32-bit and 64-bit versions of Cygwin.
I have separate "Local Package Directory"s for them, but that seems
unnecessary since almost everything is maintained separately: The 
setup binaries have different names and the mirror folders contain 
different subfolder names (x86 or x86_64). The exceptions are the
setup log files.

It would be nice if the setup.log and setup.log.full files would 
also be named (or placed in different folders) to distinguish 
between 32-bit and 64-bit versions. Then we could have the two
versions of Cygwin share the same Local Package Directory without
conflict.

Indeed, this is a low-priority item, so not worth arguing about.

--Ken Nellis

--
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