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: Wed, 12 Sep 2001 12:21:18 -0400 From: Christopher Faylor To: Cygwin-Apps AT Cygwin DOT Com Subject: Re: Mingw and w32api package names. Message-ID: <20010912122118.C17887@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> <20010911115844 DOT B12971 AT redhat DOT com> <3B9E4F56 DOT FF6B92A1 AT yahoo DOT com> <3B9F6038 DOT 36CB9E47 AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B9F6038.36CB9E47@yahoo.com> User-Agent: Mutt/1.3.21i On Wed, Sep 12, 2001 at 09:16:40AM -0400, Earnie Boyd wrote: >Earnie Boyd wrote: >> >> 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. >> > >Can I assume this to be acceptable? setup.ini is generated automatically. There is no way to just add something. If you are going to be renaming the mingw directory to mingw-runtime then I am not sure how setup.exe will deal with that. If you are going to be creating a new directory then that means there will be a mingw directory sitting around until we somehow modify setup to deal with the situation of obsoleting a package. cgf