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=HLr3cojP+iNC/qP1oYac6itR2ip2WRvTdL7otycpji0
	G7ZyB59IKtbHUUYABra8Ht5gdEZovvsadfgoZv039cEZsvRjiLowOXx6l2rPu/EM
	q1jR9RwXodKykFXczdrUc4PeEIcDXntsycA5miXbb0bWVBlCOqwHlfjmeHYSjNLo
	=
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=sylkR1NUIns2NDJ7sMxlKhdWnwM=; b=XnbXWNSeq/rllqCgj
	q8LFnhWotFS48RvQGpoeRE7ss6kzHdGv6zljQUricncG0DAq2aS/PeKeK9Aj8YwJ
	tX7nYVzUhDIw9xnhv5ZIKhQWLqkvtVxNYluVzuRKHsajtB8tWkZ1KEM9R0zG0xAq
	SPpAdFabtJ9BB9VIpoZRd6zwko=
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=-3.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS,TW_YG autolearn=ham version=3.3.1
X-Received: by 10.68.179.194 with SMTP id di2mr3789711pbc.203.1371840647539;        Fri, 21 Jun 2013 11:50:47 -0700 (PDT)
Message-ID: <51C4A08E.1020907@users.sourceforge.net>
Date: Fri, 21 Jun 2013 13:50:54 -0500
From: "Yaakov (Cygwin/X)" <yselkowitz AT users DOT sourceforge DOT net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygport limitations
References: <CABEPuQJDLjtbcLig1isTUJgb6RBCD8LNShbm9mTPcb9WM5S5fw AT mail DOT gmail DOT com> <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> <51C495E1 DOT 9040901 AT etr-usa DOT com> <51C4970D DOT 9090103 AT etr-usa DOT com>
In-Reply-To: <51C4970D.9090103@etr-usa.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 2013-06-21 13:10, Warren Young wrote:
> On 6/21/2013 12:05, Warren Young wrote:
>> With cygport, you wouldn't even need to provide sources.  We could email
>> in the new cygport file instead of an RFU.
>
> ...and patches.
>
> ...and customized .hint files, if needed.
>
> Yeah, I guess sending the .src.tar.bz2 probably is effectively required.

No, it's not.  IIUC, the eventual goal should be something that looks 
like Ports git:

http://cygwin-ports.git.sourceforge.net/

together with a buildbot.  Package maintainers would then commit their 
changes to a package's repo, which would then trigger a post-commit hook 
that would cause the package to be built with those changes.


Yaakov


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