RE: CVS setup

[Anders Truelsen]

Hi David,
I've been using CVS to control out install shield setups with spaces and all
for a couple of years now and I've never experienced any problems.
Just yesterday I created a bunch of modules with with spaces in their names
and it seemed to work just fine, though I'm getting slightly worried by now
:-/

regards
/anders


> -----Original Message-----
> From: David H. Thornley [mailto:address@hidden
> Sent: 5. april 2001 19:55
> To: Rob Helmer
> Cc: M Birch; address@hidden
> Subject: Re: CVS setup
> 
> 
> 
> 
> Rob Helmer wrote:
> > 
> > Don't check files or directories that have spaces in the names
> > into CVS. It'll cause nothing but trouble.
> > 
> I was just asked a question about InstallShield.  I'm not
> personally familiar with what it does, but apparently it
> creates a set of files of which many have spaces in their
> names, and it apparently cannot be set to do this as a
> matter of routine from pre-existing source.
> 
> If there was an InstallShield script we could use, I'd say we
> keep the sources under CVS control and not worry about the
> InstallShield stuff.  That apparently is not the case.
> 
> There are too many filenames to make it practical to manually
> insert underscores instead of spaces.  This being That Operating
> System, I don't know if it's easy to automate this process, like
> it would be in Unix.  Not that this would be the ideal solution,
> since it would entail creating the files, mangling the names,
> checking them in, checking them out, unmangling the names, and
> sending to the user.
> 
> I don't know if WinCVS handles this well.  Nor do I know how it
> handles merging between branches, which in our setup depends
> partly on tag naming conventions, and therefore is not
> straight out-of-the-box CVS.
> 
> The half-assed solution we're adopting right now is to zip
> the files into a zip file without spaces in the file name, but
> there's plenty of reasons why this is suboptimal.
> 
> Does anybody have any suggestions?
> 
> There are reasons why we're using CVS, so I'd rather not hear
> why I should drop it in favor of something unspecified.  Diatribes
> against proprietary Intel-based operating systems are unnecessary,
> unless they contain something amusing I haven't seen (or said)
> before.
> 
> 
> -- 
> David H. Thornley                          Software Engineer
> at CES International, Inc.:  address@hidden or (763)-694-2556
> at home: (612)-623-0552 or address@hidden or
> http://www.visi.com/~thornley/david/
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>