From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21133 invoked by alias); 28 May 2013 19:01:52 -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 21093 invoked by uid 89); 28 May 2013 19:01: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; Tue, 28 May 2013 19:01:51 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 0D1DD520652; Tue, 28 May 2013 21:01:49 +0200 (CEST) Date: Tue, 28 May 2013 19:01:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: [RFU] lftp Message-ID: <20130528190149.GB31309@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <7gh7q8ts46j2qla9d8k6pdc0hhpfra4pmj@4ax.com> <7gh7q8ts46j2qla9d8k6pdc0hhpfra4pmj-e09XROE/p8c@public.gmane.org> <51A4490A.2010500@users.sourceforge.net> <20130528102144.GC5264@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2013-05/txt/msg00124.txt.bz2 On May 28 14:06, Andrew Schulman wrote: > > On May 28 05:27, Andrew Schulman wrote: > > > If cygport is supposed to be putting lftp-debuginfo into its own directory, I'm > > > not sure why it isn't. > > > > It is ;) > > > > Ignore the created toplevel files, rather cd into the cygport project > > dir and then into the "dist" subdir. There you will find a proper > > package directory, neatly arranged for upload, including all setup.hint > > files. > > Hm, what do you know. > > > Yaakov, I'm wondering if it isn't time to do two things: > > > > - Create a new cygport version which does not create the toplevel > > files anymore. > > Yes, that will force those of us who haven't been following to notice that > something has changed. Expect of course a slew of "why won't cygport build my > packages any more" messages, and then we'll all know what to do again. > > > - Create a short documentation how to create the new cygport files. > > Yes please. I keep reading bits and pieces about how things we used to have to > do aren't required any more, but if it's not in the docs, it's too hard to go > back and find. Just as a sidenote, you could have a look into Yaakov's or my 64 bit package cygport files. Of my packages see, for instance, gawk, openssh and, FWIW, the cygwin package itself. The only thing you really have to keep in mind is to specify the cygport file always with the .cygport suffix: $ cygport foo almostall # Wrong $ cygport foo.cygport almostall # Correct Btw., did you notice http://cygwin.com/ml/cygwin/2013-05/msg00379.html ? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat