Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
>>> Religious view maybe...... <<< Sounds more to me like a very practical practice. In all the reading I've done I didn't realize there were so many gotchas with the CVS* add-ons / scripts / etc. I mean, I saw a small recommendation (and a stronger one for spaces in source file names) but beyond that I didn't see a lot of reasoning behind it. Of course, I've installed MY cvsnt into d:\cvs\cvsnt, with my repository d:\cvs\respositiories and temp d:\cvs\temp... all in one spot, nice and clean. :) Perhaps a candidate for updating on the wiki? Thanks, Glen Starrett -----Original Message----- From: Bo Berglund [mailto:Bo.Berglund at system3r.se] Sent: Thursday, April 10, 2003 12:18 AM To: Glen Starrett Subject: RE: [cvsnt] Re: newbie: Cannot create repository I know that it has been stated to work, however when dealing with the complete system including add-ons like ViewCvs and other things it is *much* safer to: - Install CVSNT to a 'non-spacey' path outside "Program Files" - Install whatever unix tools are used into a similar path, like c:\programs\gnuwin32 - Install Python into something like c:\programs\python22 - Same goes for CVSMailer, but I have taken care of that in the Innosetup script for CVSMailer, it won't accept a path with embedded spaces. - And for heavens sake don't put the repository into a place with embedded spaces! I have seen people creating the repository as a subdirectory to CVSNT and then having problems because of the spaces in the path. Realize that in processing the CVS scripts you are not allowed to have spaces embedded in any kind of scripted commands. CVS will treat the space as a field delimiter even if you try using quotes in Windows style to defeat the spaces. I have found this out the hard way.... There is also the new Microsoft "protection" that prohibits write access for normal users to any location below 'Program Files'. This makes it impossible to let an application write anything (like an ini file in its program folder) if it is installed there. It might seem to work as long as the admin that did the installation tests it out, but will break as soon as a normal user logs in and starts working. This applies to XP and W2000. Keeping spaces off the paths is the safest way to success even though some spaces may be tolerated in some circumstances. Having no spaces there will not break anything but a space may break some component. Religious view maybe...... /Bo -----Original Message----- From: Glen Starrett [mailto:grstarrett at cox.net] Sent: den 10 april 2003 00:47 To: bo.berglund at telia.com; cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: RE: [cvsnt] Re: newbie: Cannot create repository >>>> really depends on which tools you want to install, some of them are UNIX in origin and will sometimes barf on paths with embedded spaces. <<<< FYI--UNIX allows embedded spaces in paths, but it typically isn't done for the same reason it isn't typically done in Windows installs... some programs (especially lightly tested ones) barf on those spaces, regardless of platform. Windows has pushed the issue with the "Program Files" default path, so more programs have been tested against Windows. Glen Starrett _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs