[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: /#cvs.lock): No such file or directoryctory for <some directory inre
Re: /#cvs.lock): No such file or directoryctory for <some directory inrepository>
Wed, 18 Aug 2004 09:25:04 -0400
On 8/18/04 5:37 AM, "Jim Page - emailsystems.com" <address@hidden>
> 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.
Having done this myself before, I found that the best way to handle this was
to alter my behavior slightly. I'd edit from either platform, but if a
sandbox was checked out using a particular tool (e.g. TortoiseCVS on windows
or cvshome.org CVS on Linux) I'd only perform CVS operations using that
tool. Obviously, there's some overhead to remembering which tool you used,
but it beats troubleshooting the problems that arise when cvsnt clients and
cvshome.org clients operate on the same sandbox.
> 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.
Yeah. It sounds like cvsnt's metadata is not compatible with standard CVS.
(WinCVS uses cvsnt.) Ask on one of the cvsnt-oriented lists. There may be a
way to make it compatible. I still think I'd try to use the same tool for
CVS operations all the time, though.