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 X-Apparently-From: Message-ID: <3B9E4F56.FF6B92A1@yahoo.com> Date: Tue, 11 Sep 2001 13:52:22 -0400 From: Earnie Boyd Reply-To: CA List X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin-apps AT Cygwin DOT Com Subject: Re: Mingw and w32api package names. References: <3B9E33C6 DOT B8B10989 AT yahoo DOT com> <20010911115844 DOT B12971 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > > 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? > Adding an entry `@ mingw-runtime' seems to work ok. It would give enough time to work out the details of what to do for the `@ mingw' entry for the next release, e.g.: a post install script to remove entries from the setup control files in /etc/setup. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com