This is the mail archive of the cygwin@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: b19 and cygwin.dll


Just had to comment on this one.
I hope you're not referring to brain-dead uninstallers that simply
attempt to remove the keys that it setup at install time. I often have
to move things around because of changing source trees and the like.
Many of the uninstalls I've simply fail if it fails to find everything
that it thought it should. I'm in fovor of the dll with the exe concept.
And smarter uninstalls vis-a-vis the registry and other system settings
or files. _But_ leave my cygwin mount points alone. It took a lot of
setting up for some of them and a new release shouldn't invalidate
otherwise healthy mounts. Not to mention, what if you multiple releases.
Hence ... I think there ought to be per-release mount points or the
existing ones should be migrated to the new settings.

Just my $0.0002

	Bart

Craig Dickson wrote:
> 
> Bill Luebkert wrote:
> 
> >I don't know about the rest of the world, but I appreciate software
> >that can be installed into it's own directory tree and not use any
> >disk space under c:\windows and if possible not use any registry entries.
> >
> >This makes the all important uninstall a simple 'deltree'/'rm -rf'
> >command.  If everyone did it that way, my registry wouldn't be over
> >3MB and I wouldn't have hundreds of garbage files in the C:\windows
> >tree.
> 
> I appreciate software that comes with civilized uninstallers, which makes
> the all-important uninstall a simple couple of mouse clicks, including
> registry cleanup, removal of shared files that are no longer being used by
> other applications, removal of Start menu entries, etc. In the Windows
> environment, 'deltree' is a pretty simplistic way to remove software. The
> registry is there to be used by software, and should be used, though only
> for fairly small amounts of data per application. But there should be
> uninstallers, and they should remove registry keys created by the program
> being uninstalled.
> 
> Given that the various GNUWIN32 programs need to be on the path somewhere in
> order to be reachable by the shell, it makes perfect sense to me to put
> cygwin32.dll in the same directory as the core GNUWIN32 tools. I don't see
> any benefit to putting it in the system directory. So I agree with you on
> that point, though for another reason.
> 
> Craig
> 
>     ---------------------------------------------------------------
> 
>                                 Name: Craig Dickson.vcf
>                  Part 1.2       Type: text/x-vcard
>                             Encoding: quoted-printable

-- 
Bartlee A. Anderson     System Test (Interfaces-Tools-Automation-ISDN)
Rockwell International                    Electronic Commerce Division
300 Bauman Ct.                                banders@ecd.rockwell.com
MS 933-605      Opinions my own, not Rockwell's   VOICE (630) 227-8975
Wood Dale, IL 60191                               FAX   (630) 227-9771
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]