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, 11 Sep 2001 11:58:44 -0400 From: Christopher Faylor To: Cygwin-Apps AT Cygwin DOT Com Subject: Re: Mingw and w32api package names. Message-ID: <20010911115844.B12971@redhat.com> Reply-To: cygwin-apps AT Cygwin DOT Com Mail-Followup-To: Cygwin-Apps AT Cygwin DOT Com References: <3B9E33C6 DOT B8B10989 AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B9E33C6.B8B10989@yahoo.com> User-Agent: Mutt/1.3.21i On Tue, Sep 11, 2001 at 11:54:46AM -0400, Earnie Boyd wrote: >Shortly I'll be releasing new packages for MinGW and w32api. The >current file name for MinGW isn't really reflective of the package name >itself. I would like to use mingw-runtime-$(VERSION)-$(CYGRELEASE) for >the name. I would also like to use w32api-$(VERSION)-$(CYGRELEASE) for >the w32api package name. This is more consistent with the packaging and >is more consistent with the way the packages are distributed by the >MinGW team. Comments or objections? I'm sure that this it will confuse the current version of setup if you call this mingw-runtime. How are you planning on dealing with the changeover? cgf