From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3451 invoked by alias); 23 Oct 2013 17:42:08 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 3419 invoked by uid 89); 23 Oct 2013 17:42:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-HELO: mho-01-ewr.mailhop.org Received: from mho-03-ewr.mailhop.org (HELO mho-01-ewr.mailhop.org) (204.13.248.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 23 Oct 2013 17:42:07 +0000 Received: from pool-98-110-183-69.bstnma.fios.verizon.net ([98.110.183.69] helo=cgf.cx) by mho-01-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1VZ2RZ-000Lvu-RX for cygwin-apps@cygwin.com; Wed, 23 Oct 2013 17:42:05 +0000 Received: from cgf.cx (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 5D70360103 for ; Wed, 23 Oct 2013 13:42:05 -0400 (EDT) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18wAYX/jrTLJ0P3NggnQiw9 Date: Wed, 23 Oct 2013 17:42:00 -0000 From: Christopher Faylor To: cygwin-apps@cygwin.com Subject: Re: Testing ping for cygwin x86_64 Message-ID: <20131023174205.GA1619@ednor.casa.cgf.cx> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <20131017185430.GB23477@calimero.vinschen.de> <20131023075856.GA4712@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131023075856.GA4712@calimero.vinschen.de> User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2013-10/txt/msg00197.txt.bz2 On Wed, Oct 23, 2013 at 09:58:56AM +0200, Corinna Vinschen wrote: >On Oct 22 22:49, Balaji wrote: >> On Thu, Oct 17, 2013 at 11:54 AM, Corinna Vinschen wrote: >> > On Oct 17 10:17, Balaji wrote: >> [...] >> >> This being my first attempt at trying to possibly maintain a Cygwin >> >> package, I want make sure I'm doing the right thing. One odd thing is >> >> that all of the source code and Makefile are in the patch file. Also, >> >> am I free to convert the package to cygport/ditch the shell script >> >> etc. - I understand all that may typically be the maintainer's choice? >> >> Advance thanks for any advice from you seasoned veterans. >> > >> > Porting a package to cygport is highly appreciated, no worries. And of >> > course you are free to pack it in a cleaner fashion than the existing >> > package. >> >> One other question - I remember there was some discussion about noarch >> packages a while ago. Are there any rules for/against making something >> a noarch package. And the associated pros/cons - both from a >> maintainer and user perspective? > >Noarch packages are fine, but the packaging mechanism doesn't support >them the same way as in Linux distros. They still have to show up >twice, once in the 32 and once in the 64 bit release area. i.e., just like Linux distros do. cgf