This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: RFC: setup.ini change
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 29 Apr 2002 11:27:48 -0400
- Subject: Re: RFC: setup.ini change
- References: <01c001c1ef81$bb425230$0200a8c0@lifelesswks>
- Reply-to: cygwin-apps at cygwin dot com
Given the way that md5 checksums are generated on sourceware currently,
this would be a problem. The checksums are generated asynchronously
with the creation of setup.ini.
I would prefer the three column version of install/source, though.
Slightly less work for me.
cgf
On Mon, Apr 29, 2002 at 11:28:20PM +1000, Robert Collins wrote:
>I'd like to change this:
>install: release/bash/bash-20000901.tar.bz2 276403
>source: release/bash/bash-20000901-src.tar.bz2 1892899
>
>to
>
>install: release/bash/bash-20000901.tar.bz2 276403
>158044165a04791968a7e7fc8daaef9e
>source: release/bash/bash-20000901-src.tar.bz2 1892899
>158044165a04791968a7e7fc8daaef9f
>
>or
>
>install: release/bash/bash-20000901.tar.bz2 276403
>install-md5: 158044165a04791968a7e7fc8daaef9e
>source: release/bash/bash-20000901-src.tar.bz2 1892899
>source-md5: 158044165a04791968a7e7fc8daaef9f
>
>I don't care which we choose. My preference is the first one - it will
>keep the files smaller. Either will cause setup.exe to barf when first
>introduced. Likewise for third party parsers that are ... pedantic.
>
>To help deal with this I suggest the following approach:
>with the new version I want to release, we include the new format ini
>parser, but do nothing with the data. Then we can introduce features to
>use it at our leisure.
>
>Any preference folk?
>
>Rob