On Wed, Oct 13, 2004 at 12:11:05AM +0200, Bas van Gompel wrote: >Op Sun, 10 Oct 2004 13:13:23 -0400 schreef Christopher Faylor >in <[EMAIL PROTECTED]>: >: On Sun, Oct 10, 2004 at 08:36:38AM +0200, Bas van Gompel wrote: >: > Op Sat, 9 Oct 2004 19:18:13 -0400 schreef Christopher Faylor >: > So cygcheck will have the same problem... >: >: Right, but cygcheck can rely on the fact that cygwin1.dll is around, at >: least, if necessary. > >The dll is/should be around after setup ran (in install-mode), as well.
Right. But it may not be loadable. I don't know if you can still use LoadLibrary on dlls which lack the correct permissions or not. >: I guess a goal could be to come up with a generic >: library which did sanity checking and corrections on cygwin permissions. > >Which would than have to be linked statically, or suffer from it's >own permission-problems... Right. >: > How about doing it from a (postinstall-)script? >: >: A post-install script doesn't help if someone copied all of their stuff >: to a CD-ROM and then to a new system. > >I didn't think that was a supported procedure. (IOW: YOWTWYWT) If we are just going to worry about people doing things perfectly with setup.exe then we hardly need cygcheck at all. cygcheck reports on things that you can get from other utilities. In fact, cygcheck doesn't really need to be a mingw program if we can rely on the fact that everything is ok on the system. >A post-install script does have the advantage of being run from within >cygwin. You seem to be arguing for a post-install script when I've already said that it would be a good idea to have a post-install script. cgf
