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 Message-ID: <3BA00966.3080900@ece.gatech.edu> Date: Wed, 12 Sep 2001 21:18:30 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin-apps AT Cygwin DOT Com Subject: Re: Mingw and w32api package names. References: <3B9FD44B DOT 3353 DOT AE9D806 AT localhost> <3B9FC725 DOT 265FB04F AT yahoo DOT com> <20010912210823 DOT A26480 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > On Wed, Sep 12, 2001 at 04:35:49PM -0400, Earnie Boyd wrote: > >>"Gerrit P. Haase" wrote: >> >>>I wonder why it is neccessary to 'rename' a package. >>>There will be two packages in future? Runtime and Devel? >>> >>> >>For consistency. The package is distributed by MinGW.org as >>mingw-runtime-$(VERSION). The new package will supersede the old one. >> > > Maybe the best thing to do is, as others (Chuck?) have suggested, keep > the mingw directory but put a new, empty .tar.bz2 file in it. That will > cause the old mingw stuff to be uninstalled. > > Then, make a new mingw-runtime directory and just put the tar balls there. > > Then, in a couple of months we can delete the mingw directory entirely. > > If you could verify that this does the "right thing", Earnie, I think this > is the way to go. I don't see any other way to handle this. You just have to make sure that users FIRST update mingw to the "new" empty version, and SECOND install mingw-runtime. Of course, since setup does things in alphabetic order, if you select both at the same time, it will get done in the proper order. --Chuck