hi, I don't know if your patch actually does something useful because I don't know much about windows ... :-) I'll wait for Adam - who knows about windows - to rule on this matter_
but I want to address immediately the performance problems it might cause [on unix machines as well] ... running subshells and firing sed commands must be avoided in the processing mainstream ... I'd rather remove the check altogether if that is the only way of performing it_ we might either completely remove the check at all on all machines, or disable it on windows [and any other system where it is too computationally expensive], or you need to figure out a way to perform the check without running additional subshell commands_ the check is pretty irrelevant, and I added it because it was so computationally cheap on unix ... and hoped it might prevent some unaware people from complaining that the test service in gnustep-gui didn't work because they hadn't run the GNUstep.sh script ... or had run it but then messed so much with users that they no longer had the GNUstep tools in their path ... but I have nothing particular against completely removing the check if it is too expensive to perform_ my preferred solution would be to enclose the check into a ifneq ($(findstring cygwin, $(GNUSTEP_TARGET_OS)), cygwin) endif so that it is not performed at all on windows, and is performed only on systems were it is irrelevantly quick_ comments appreciated_ _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
