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 13:16:05 -0400 From: Christopher Faylor To: cygwin-apps AT Cygwin DOT Com Subject: Re: Mingw and w32api package names. Message-ID: <20010912131605.A18485@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> <20010912122118 DOT C17887 AT redhat DOT com> <3B9F8E93 DOT 4130F2D2 AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B9F8E93.4130F2D2@yahoo.com> User-Agent: Mutt/1.3.21i On Wed, Sep 12, 2001 at 12:34:27PM -0400, Earnie Boyd wrote: >Christopher Faylor wrote: >> 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. > >According to Chuck's response the autoscript will create an `@ >mingw-runtime' entry even if the directory is named mingw. If you create a setup.hint file with a: curr mingw-runtime-NNNNNN.tar.bz2 it will override the mingw name from the directory. I don't know how that solves any problems, though. There will still be an orphaned 'mingw' on people's systems. This is functionally equivalent to renaming the directory, I think. cgf