From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28749 invoked by alias); 24 Jun 2013 09:13:52 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 28739 invoked by uid 89); 24 Jun 2013 09:13:52 -0000 X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,TW_YG autolearn=ham version=3.3.1 Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 24 Jun 2013 09:13:51 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 103715200DD; Mon, 24 Jun 2013 11:13:49 +0200 (CEST) Date: Mon, 24 Jun 2013 09:17:00 -0000 From: Corinna Vinschen 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: <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) X-SW-Source: 2013-06/txt/msg00610.txt.bz2 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