Re: CVS setup

[Rob Helmer]

Hi David,


Maybe you can use a commitinfo script to do this. I'm not
really sure, I know people use them to strip CRs from files,
I imagine you could automatically remove spaces like this
somehow.

Perhaps you could automatically convert them back on checkout.
I'm not sure how this part would be done, but if you wanted
to do such a thing I guess you would use a character that is
unlikely ( or against procedure ) to have in any other checked-in
file.

If your CVS client can handle the spaces, you may be ok without
this hackery.

I know the CVS CLI doesn't deal well with them ( WinCVS
uses a ported version of the UNIX CLI ). I'm not sure what
other implications there are, maybe someone who's run into
such situations could comment here.

I'm not sure why you would check InstallShield files into
CVS, but as you've clearly stated that you intend to use
CVS, and intend to have spaces in the filenames, I hope this
helps you somehow.



--
Rob Helmer
Namodn

On Thu, Apr 05, 2001 at 12:54:43PM -0500, David H. Thornley wrote:
> 
> 
> 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
>