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=Dg52L5LsUlQJppre3ADiZ/tIDpVRGQX+rnf1tdTv55fBxFoE+2o3i
	g3TH/eNRT1knFDz7LP4iVUnyirn5hk6NHG0nu1OKTpi0sBkYC3UihWd0/FEvwaPD
	RlIape0nA6Zck/C4jfj18ACoY1jmalH9i2olVtm+RFpByMLUuB73bQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Mon, 24 Jun 2013 11:13:49 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygport limitations
Message-ID: <20130624091349.GC14319@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CABEPuQJJpRfPKSwZ7M0eTOdp1HxDcmvuy1=qXFHBw-8kLkZ1ZQ@mail.gmail.com> <51C0D956.4090905@etr-usa.com> <51C1B299.1000701@cwilson.fastmail.fm> <51C1F0F9.70601@etr-usa.com> <51C1FA8E.3000307@users.sourceforge.net> <51C33F38.4080103@etr-usa.com> <20130620181056.GA16923@calimero.vinschen.de> <51C495E1.9040901@etr-usa.com> <51C4970D.9090103@etr-usa.com> <51C4A08E.1020907@users.sourceforge.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <51C4A08E.1020907@users.sourceforge.net>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Jun 21 13:50, Yaakov (Cygwin/X) wrote:
> 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.

Yes, that sounds good.  The last discussions in my dept about setting up
a build system are long gone, so we have to start anew.  This will take
some time (think unsavory things like budgets and so on...), but I'll
keep on it.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

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