| delorie.com/archives/browse.cgi | search |
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
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |