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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=PsQ+Ak1sEDJ9Yj8ClYHJvZDgwTLETlb+1ASQT+iGhCo
	xmkB7axg4YdxQKLMNBdALY7HUtM9OgMEdV6LkIOKi5rgcz8OC+qOfk/vOM6fciFV
	uSX2sIaORs5AuhLMnAtvNCHsUstVbYMtCZK9tzY9k1QUUU82yUvMocI3iV9zpH/k
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=ner8MJZ3o1Xv0wNHSGT51WgDzE0=; b=MiGnmD1vNt1LT6izG
	TpKKOivmJGrnnYJRuxEKuLgAqrPojN3aj0TWVb77EeGxUH876x+ZKvY5hkcikyni
	XLpEw3rZPMDSo9HHyIpfAwc9dqS13K3gtXsJGB960V5F+eROeHwmOokaKFFkG7eG
	bDYRySe5tJYtZFyJxNYOgauymg=
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.2 required=5.0 tests=AWL,BAYES_20,FREEMAIL_FROM,KAM_COUK,SPF_PASS autolearn=no version=3.3.2
X-HELO:	out.ipsmtp3nec.opaltelecom.net
X-SMTPAUTH:	drstacey AT tiscali DOT co DOT uk
X-IronPort-Anti-Spam-Filtered:	true
X-IronPort-Anti-Spam-Result:	ApMBAFL3ElNV0kxR/2dsb2JhbAANTcItgwyBKIMZAQEBBDhAEQsSBgkWDwkDAgECATcOEwgBAbIhoSsXjmAWhCIErhQ
X-IPAS-Result:	ApMBAFL3ElNV0kxR/2dsb2JhbAANTcItgwyBKIMZAQEBBDhAEQsSBgkWDwkDAgECATcOEwgBAbIhoSsXjmAWhCIErhQ
Message-ID:	<5312F78F.1090508@tiscali.co.uk>
Date:	Sun, 02 Mar 2014 09:19:11 +0000
From:	David Stacey <drstacey AT tiscali DOT co DOT uk>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Unpacking 7z archives on Cygwin64
References:	<73E88645491D4727952D7C498CF24DA7 AT TKsamsung>
In-Reply-To:	<73E88645491D4727952D7C498CF24DA7@TKsamsung>
X-IsSubscribed:	yes

On 02/03/14 07:26, Tony Kelman wrote:
> I'm still not clear, do 64 bit packages have their own independent
> set of patches, or is it necessary to write patches that work for
> both 32 bit and 64 bit?

This is really up to the package maintainer. Personally, I prefer to 
have one cygport file and patch set that builds both sources. I test 
uname(1) if I need something specific for one architecture. This means 
that I can keep my cygport files and patches in version control and have 
two instances checked out, one for each architecture. It also means that 
the source tarball is generic. The downside is that I can't 
cross-compile. However, I'm sure that there are a number of maintainers 
who will do things differently.

On the subject of maintainers, p7zip does have one; it is really up to 
Mr. Wilson to prepare a 64-bit version whenever he is ready to do so. 
I'm sure he'll appreciate the work that you've done in getting this far. 
That said, we have precedent for some 'non-maintainer uploads' for 
64-bit, just to make up the numbers and fill some important gaps.

Cheers,

Dave.


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