From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 76410 invoked by alias); 3 Sep 2016 22:43:36 -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 76401 invoked by uid 89); 3 Sep 2016 22:43:35 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_COUK,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:731, her, online, central X-HELO: smtp-out-6.tiscali.co.uk Received: from smtp-out-6.tiscali.co.uk (HELO smtp-out-6.tiscali.co.uk) (62.24.135.134) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 03 Sep 2016 22:43:25 +0000 Received: from [192.168.1.5] ([79.68.214.249]) by smtp.talktalk.net with SMTP id gJegbDgqv3OBfgJekbKFmG; Sat, 03 Sep 2016 23:43:23 +0100 Subject: Re: [ANNOUNCEMENT] boost 1.60.0-1 To: cygwin@cygwin.com References: <5acf2494-0351-bba7-7672-662c2fe10767@cygwin.com> <20c46098-6fff-d4d4-8b99-9bd818823c54@gmail.com> From: David Stacey Message-ID: Date: Sat, 03 Sep 2016 22:43:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20c46098-6fff-d4d4-8b99-9bd818823c54@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfKnK22V8Xxw/ZH9Do5CYjFC81L7usfd4NxqXWp/qZKkSlGqL1XMM2hdIUzQeYAIPxXwAIyukO6aaO0iG6ELH/2TdUAIokmcF8BM354GG0/l4whVcHdOt M8usoXg3N/xMadHVE4dOiBFSj1dS3kk9z3Efk0ZX0/Gum3ef766O8hbc X-IsSubscribed: yes X-SW-Source: 2016-09/txt/msg00053.txt.bz2 On 03/09/16 15:24, Marco Atzeri wrote: > On 03/09/2016 11:39, David Stacey wrote: >> On 02/09/16 23:48, Yaakov Selkowitz wrote: >>> Or, wrt my packages (and that's it atm) the .cygport and patches are >>> also online: >>> >>> https://github.com/cygwinports/boost >> >> Could / should other package maintainers be using this repo? >> > > Why ? > > We don't have currently a central repository. A central repo of cygport files and patches would be one step on the long road to an automated build system - always assuming that's something we'd like to move towards. > Every maintainer is using his/her own solution. Quite. Mine are in a private svn repo at the moment, but I could switch. Dave. -- 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