Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Tue, 16 Oct 2001 22:05:42 +0200 From: Corinna Vinschen To: cygwin-apps AT cygwin DOT com Subject: Re: cURL packaging progress Message-ID: <20011016220542.K1696@cygbert.vinschen.de> Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <6EB31774D39507408D04392F40A10B2BACC611 AT FDYEXC202 DOT mgroupnet DOT com> <3BCCA532 DOT 13453 DOT 17EEA44 AT localhost> <20011016153627 DOT A11848 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011016153627.A11848@redhat.com>; from cgf@redhat.com on Tue, Oct 16, 2001 at 03:36:27PM -0400 On Tue, Oct 16, 2001 at 03:36:27PM -0400, Christopher Faylor wrote: > On Tue, Oct 16, 2001 at 09:22:58PM +0200, Gerrit P. Haase wrote: > >> Roth, Kevin P. schrieb am 2001-10-16 15:00: > >>I had already realized this convention. My question had more > >>to do with creating the build scripts. In Solaris, you have > >>"pkgadd" modules, in Linux you have RPM's... In Cygwin, is there > >>any standard name for a cygwin binary tarball? > > > >Not that I'm aware of at the moment. > > I'm still not exactly sure what you're asking. The tar files will be > named with the package name ("curl"), the version (1.2.3), and the > release number (1 in this case). So, your release will be > curl-1.2.3.tar.bz2 (note that it should be bzipped). Oops, Chris missed the release number in the example: curl-1.2.3-1.tar.bz2 The source analogous curl-1.2.3-1-src.tar.bz2 The source should unpack into a directory exactly named as the archive curl-1.2.3-1/ Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc.