.eomodeld~ directory and CVS: annoying problems
.eomodeld~ directory and CVS: annoying problems
- Subject: .eomodeld~ directory and CVS: annoying problems
- From: Jonathan Rochkind <email@hidden>
- Date: Tue, 6 Apr 2004 14:40:50 -0500
There's something really annoying about the way EOModeler makes
.eomodeld backups of the model files, and the way it interacts with
CVS. This just bit me big time, I just realized.
When you save a copy of your model in EOModeler, the app first moves
the previous version of the model (in a directory/package ending in
.eomodeld) aside to create a backup, ending in .eomodeld~, note the
tilde.
The problem is that if the model is under CVS control, it contains a
"CVS" directory, and this CVS directory is put in the backup folder
too. The CVS directory is also properly in the newly saved .eomodeld
directory (I recall EOModeler used to have a problem with that). But
now there are TWO identical CVS directories, one in the actual
.eomodeld model, and one in the .eomodeld~ backup.
Why is this a problem? Well, I do a CVS commit on the _project
directory_ as a whole. This is a reasonable thing to do---I've made a
bunch of changes to the project, and want to commit any changes I
have made. But now the CVS client goes through all the
sub-directories and commits them all. It gets to the .eomodeld, and
commits my changes---good. But THEN it goes to the .eomodeld~ backup
directory, it finds a CVS folder there, so it commits that too! And
the CVS folder there, since it was copied from the original .eomodeld
directory, causes the "backup" files to essentially be committed _on
top of_ my actual changes from the original .eomodeld, essentially
over-writing those changes in CVS. Now in CVS, I've got the _old_
version of the EOModel files committed! When I update somewhere
else---or even next time I update this working copy---I don't get the
EOModel files I meant to commit, I get the old version from the
.eomodeld backup!
This is very bad, and leads to very mysterious problems, of course.
I can't be the only one who has run into this. I am wondering how
other people handle it. I am not using PB/XCode as my CVS client,
I'm using a third party CVS client; if using PB/XCode CVS client
changes things, let me know how.
It strikes me that I am only sometimes bitten by this problem.
Probably because sometimes I end up saving in EOModeler multiple
times, so the .eomodeld~ backup directory ends up being identical to
the actual .eomodeld directory---and so doesn't cause a problem on
CVS commit. I suppose that's one solution, always save TWICE, to
essentially make the .eomodeld~ backup useless, and not creating
problems. But that's annoying; sometimes I'm sure I or another
developer will forget to save twice, and run into the problem. If I
could disable EOModeler's making of an .eomodeld~ backup entirely,
that would be nice, but there doesn't seem to be a way to do that.
Others must have run into this?
--Jonathan
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.