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=hTBO/Vcub+K8jfa2EsJewRXoT6YgryfInlwinzLv1R1tAwNNep9jb
	Ie9gtOkp3IJ6zYdgVbPQgflEoEyO05WtyL+HrJNTEp79ELl27yt6ZXz8OQ/xlDOw
	Zx5DksQiBKMKRLgaZpo2Lda4tPpTaoxcKPlUa0uv1PymOJ1TkM19eI=
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=cNnCwq8DFU3/eHjzN8BM10DaEP0=; b=Z0C07sehJ7u8KG5RZBxCH1GoUkmm
	WI085luS/NDrWRpBXcqtqkFn+Px0wCWUsIxpsKqf3lrWztNZ1SFiaYvNw+Lv5Kdx
	HpdF1SmAUcFZFBxOyvza+9fOvuJP4UItVb1mBHShQ/30ATm/zMqDgltXGrNd7vcj
	oOaSxiUT8DYa4RU=
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.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,TW_YG 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:	U2FsdGVkX19LMMB4Hfq74Cfx/+kyIzIN
Date:	Fri, 21 Jun 2013 10:34:11 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: cygport limitations (was: Adding MSYS functionality to Cygwin)
Message-ID:	<20130621143411.GA5918@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<51C0B08E DOT 8080900 AT etr-usa DOT com> <CABEPuQJJpRfPKSwZ7M0eTOdp1HxDcmvuy1=qXFHBw-8kLkZ1ZQ AT mail DOT gmail DOT com> <51C0D956 DOT 4090905 AT etr-usa DOT com> <51C1B299 DOT 1000701 AT cwilson DOT fastmail DOT fm> <51C1F0F9 DOT 70601 AT etr-usa DOT com> <51C1FA8E DOT 3000307 AT users DOT sourceforge DOT net> <51C33F38 DOT 4080103 AT etr-usa DOT com> <20130620181056 DOT GA16923 AT calimero DOT vinschen DOT de> <74f7s89jvij7188akllq0l4qpp0i2ju35q AT 4ax DOT com> <20130621074934 DOT GF1620 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
In-Reply-To:	<20130621074934.GF1620@calimero.vinschen.de>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Fri, Jun 21, 2013 at 09:49:34AM +0200, Corinna Vinschen wrote:
>On Jun 20 22:38, Andrew Schulman wrote:
>> >   If every maintainer would use cygport, it would allow us to change
>> >   the build method to one along the lines of most Linux distros.
>> >   In Linux distros, the maintainer provides only the spec file and
>> >   the source archive.  The actual build for all supported platforms 
>> >   could be done on a machine which creates the distro from there.
>> 
>> That would be cool.  Let's do it!
>
>Uhm, that was a projection into the ideal future.  No provisions have
>been made yet.  We need to set up a central repository like Yaakov's
>cygwinports git repo and a central build mechanism.  The first we can
>probably shamelessly copy from Yaakov and set up over the next few
>months, the second needs a bit of hacking.

I'm not sure if this reminder is needed but, I'm not switching to
cygport and I believe there are also a couple of other people using
non-cygport packagers as well.

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