C:\Scmbug is the *wrong* place to put *anything* in windows. first of all, for your comment in another message, i'd like to remind you that 95% of the universe *is* windows. more likely than not, most scmbug installations are on windows. secondly, windows users didn't decide about the Program Files directory. microsoft did, and it's the same directory since Win95. the drive letter is, as you know, inherited from DOS, and i assume it would be difficult to get rid of it without breaking 90% of windows programs. i don't think it would be a big problem if you'll ignore the x86 folder in win64 and install to the %ProgramFiles% folder. one way i could think of doing this is put a setup.bat file in the zip file, that will copy the files to the right place. the least you could do, is remove the drive letter from the path in the zip. i am certain there are people who constantly have to work around this, because their program files folder is on another drive.
the user doesn't set the enviroment variable. it's set by the system, and i assume any system that doesn't have this variable set will have lots more problems than how to install scmbug. tsahi -- The day Micro$oft sells something that doesn't SUCK is the day they start selling vacuum cleaners. http://www.geocities.com/tsahi_75 ----- Original Message ---- > From: Kristis Makris <[EMAIL PROTECTED]> > To: Thorsten Schöning <[EMAIL PROTECTED]> > Cc: [email protected] > Sent: Thursday, December 13, 2007 6:49:08 PM > Subject: Re: Re[4]: [scmbug-users] error in parameter to diff on win64 > > On Thu, 2007-12-13 at 10:49 +0100, Thorsten Schöning wrote: > > into the normal config for SCMBug. A Zip-file decompressed in some > > directory by the user with maybe changing some configuration is > a > more > > easy way do distribute SCMBug, in my oppinion. A checkout from CVS or > > Subversion should be more elegant, too. > > I see where you are going with this. We could not use absolute paths in > the .pm files and call the hooks with ' perl -L'. > (Remember ??? Having a config option won't help us here. We still need > to call the hooks to start the glue). It would be easier for a user to > change the installation path in the hooks, and also easier for a > user > to > break the installation path in the hooks, and it doesn't solve the > problem that a single absolute installation path needs to be agreed on > beforehand. I'd rather not use an environment variable, since that > relies on the user setting the variable. > > I'm becoming more convinced we should install in C:\Scmbug. > > ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
