[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: /#cvs.lock): No such file or directoryctory for <some directory inre

From: Jim Page -
Subject: Re: /#cvs.lock): No such file or directoryctory for <some directory inrepository>
Date: Wed, 18 Aug 2004 11:37:38 +0200

Hi Doug

Thanks for your input. I think I hold a minority position here, but I would
just like to add my comments in case I didn't communicate my position well
and you misunderstood me.

> > What you are suggesting, and is also suggested in the above postings, is
> > having 2 sandboxes, 1 linux and 1 windows, right? Ok but it sounds like
> > typical case of us working round the tools rather than them working for
> Actually, since line endings are different between Windows and Linux,
> I don't see how you could safely do any different:  If you edit in
> Windows and Alice edits in Linux and you share a directory, chances
> are extremely high that Alice will introduce lines with missing CR's
> and you'll introduce lines with extra CR characters.  To me, it's a
> bit like this:  If you check out in English and she checks out in
> Spanish, you can't really use the same checkout without getting
> gibberish. <grin>

That's true except that most decent editors (the ones we use anyway) can be
set to detect line ending type and stick with it, and we standardise on unix
line endings. The only time we encounter problems like this is where someone
hasn't got their editor set up right, and that can be fixed as a one-off
with dos2unix. I believe we have the line-endings-in-source issues dealt
with, or at least at a manageable minimum, and we have run ok for 2 years or
so. My problem here is the cvs tools writing their system files differently
according to OS, which doesn't seem a good idea to me.

I think I have expressed myself badly. Our developers are working on both
windows and linux -at the same time-. Either with 2 dev boxes, or using
VMware to run the other OS, with a partition shared between the 2. What is
being suggested here is using commit to propogate changes between a given
developer's OS-specific sandboxes during development. I am talking here
about 'ok that fix builds under windows, lets see if builds under linux'. In
our case right now this class of commit would not be done, and I can't see
how this won't lead to an increased risk of nonsense in the repository.
Maybe I'm splitting hairs but even if the risk is small it just doesn't seem
a good idea. I can't believe our situation is all that rare.

Now I have written that I'm starting to think that I am complaining in the
wrong place. It is probably WinCVS or another product that is writing these
badly formatted files. linux cvs broke, and I posted a message concerning
how to fix it, but it is not to blame if some other product it messing up
its files! Hmm. My apologies for wasting everyone's time.


Email the way you want it - scanned for viruses and unwanted content by 

Information regarding this service can be found at

reply via email to

[Prev in Thread] Current Thread [Next in Thread]