Date: Sun, 22 Jul 2001 13:57:12 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Andrew Cottrell cc: djgpp-workers AT delorie DOT com Subject: Re: Comments on GCC 3.0 distribution In-Reply-To: <002b01c11244$3d9e86c0$0a02a8c0@acceleron> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, 22 Jul 2001, Andrew Cottrell wrote: > > > In either case the non technical end users will still make mistakes. > > > > If we replace the packages on SimTel with patched ones, what mistakes > > should that cause? > > The end users will say they have the correct version of the package by > checking the version via the version option in most exe's, but this does not > indicate that the package was re-built with the modified libc. People who already downloaded the packages either don't use them on W2K or somehow aren't prone to the problems we were trying to solve. People who will download the packages after we update them will not be prone to those bugs. So the only problem that would be left behind are with users who downloaded the old versions, but will discover the bugs only in the future (e.g., because they still haven't use the affected programs). We can simply tell them to reinstall when they complain. > I see this as > causing allot of problems with end users using the old packages on Win2K > instead of the newer packages with the same name. Experience shows that updating a package without changing the version tends to have very few problems. As a matter of fact, Mark just did that with Binutils (to correct a minor problem with Info files). > A suggestion is to include a line in the manifest, dsm, readme or a new file > in teh package that explicitly outlines the other packages and versions that > were used to build the package. Yes, I agree.