delorie.com/archives/browse.cgi | search |
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=n5q0LaYf3Kbr68mq54OcH78mujmE5rzO7GT23KtqP4g3058ZxqGdd | |
JcOIYWoHf2UdxFBjLpQDcUWMCNdkpLRvWOS4FPJ6JIYSGaH3mml0MQnAdVqHpvDi | |
bMVrz3KvyeJJf0VtkTf1JXqJy7Gd/vv73BPw/zmHHV6RymZShQmVMI= | |
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=g2PWqmiMW/i0ChEl6p//fSn52Qo=; b=qqeOqLXijHwrAgZKzniMqwImaaF1 | |
L/0qe8165pvmd3Ln/ZUvT//ISNOI+fUY4FZ5qhfOi6mEyyjPVvHb88vaE9Eh1GcR | |
fQnG5RypELJd1B5Jn4SqIYJNkeKrgIdf+jBJinAKtMtjXB8n2qEJuwOJ2rqKzQp6 | |
WUW5pGoLWDGRKAk= | |
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.8 required=5.0 tests=AWL,BAYES_00,TW_YG autolearn=ham version=3.3.1 |
Date: | Fri, 21 Jun 2013 09:49:34 +0200 |
From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: cygport limitations (was: Adding MSYS functionality to Cygwin) |
Message-ID: | <20130621074934.GF1620@calimero.vinschen.de> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
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> <74f7s89jvij7188akllq0l4qpp0i2ju35q AT 4ax DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <74f7s89jvij7188akllq0l4qpp0i2ju35q@4ax.com> |
User-Agent: | Mutt/1.5.21 (2010-09-15) |
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. 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |