This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: Restructuring gettext
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-apps at cygwin dot com
- Date: Fri, 4 Jan 2002 11:51:03 -0500
- Subject: Re: Restructuring gettext
- References: <3C18EBA9.9030102@ece.gatech.edu> <0b5501c184be$8639eb80$0200a8c0@lifelesswks> <3C1A35F6.8050909@ece.gatech.edu> <0f8901c185fc$a108b600$0200a8c0@lifelesswks> <3C1D5F00.3010506@ece.gatech.edu> <3C3384B2.8070305@home.com> <20020103002446.GA8508@redhat.com> <3C35CD04.8070902@home.com>
- Reply-to: cygwin-apps at cygwin dot com
On Fri, Jan 04, 2002 at 10:40:52AM -0500, David A. Cobb wrote:
>Christopher Faylor wrote:
>
>>On Wed, Jan 02, 2002 at 05:07:46PM -0500, David A. Cobb wrote:
>>
>>>Charles Wilson wrote:
>>>>it occurs. (Perhaps upgrades of currently installed packages should
>>>>ALWAYS precede installation of new packages?)
>>>>
>>>
>>>I've had cases like this in another context and found the most
>>>straightforward solution is for (setup.exe) to do any uninstalls first,
>>>then any reinstalls, then everything else. This would also have saved a
>>>few shot toes when libncurses#n came out (I thin`).
>>>
>>
>>I've thought about suggesting the same thing but the problem with that
>>scenario is that if you cancel an installation, then all sorts of stuff
>>is uninstalled -- which probably isn't what you expected.
>
>Probably not. But "cancel" at what point in the process? It's *real*
>hard to program an installation procedure that's robust in the face of a
>user clicking the "cancel" button in the middle. Even the
>"professional" packages are likely to barf.
The "professional" installers aren't installing a number of disparate packages.
I don't think it is unreasonable to assume that if I cancel a gcc installation
my current binutils setup will still be intact.
cgf