Jikes RVM

I went ahead and removed the .cvsignore files. Hopefully this won't cause
too much problem for rsync backup. We'd started to use the ignore property
so the two were getting out of sync.

Logged In: YES
user_id=27364

> I don't see that this is any more work than writing
> a script that updates svn properties based on the contents
> of .cvsignore files.

I guess the main difference is that I have to crawl all the
directories to be backed up to create a large exclude file.
Fortunately,
svn's support for offline "svn status" means it has have
this ignore information locally. A quick grep shows it is in
.svn/dir-props. Googling it seems like a lot of people are
having this problem but rsync itself seems to be the place
to fix it... and there doesn't seem to be any discussion
there about it with the rsync people. I guess I'll be
implementing my own svn:ignore handling instead to deal with
all the third party svn repositories out there. Our way
meant our users didn't have to change their behavior and a
post-commit script could keep things in sync but we have to
deal with others standard use of svn.

Logged In: YES
user_id=1642927

There was inconsistencies between the .cvsignore files in
subversion and the svn:ignore properties specified. I guess
it is natural that the subversion property is more upto date
given that is the "native" format the source control system
works with.

Admittedly you could not use --cvs-ignore with rsync -
instead you use --exclude-from=FILE and generate FILE via a
script. I don't see that this is any more work than writing
a script that updates svn properties based on the contents
of .cvsignore files. It also keeps the subversion repo clean
of duplicated data.

Logged In: YES
user_id=27364

I think the bug is that SVN does not support .cvsignore files :)

People who use rsync for backups usually use its --cvsignore
feature to exclude generated build files.
It is not clear that it would be easy for rsync to look at
svn properties to have a similar feature for svn.
Perhaps it could look at the .svn directory to find this
information.

My own projects at Stanford have kept the .cvsignore files
and use them as the source of truth for what to ignore.
rsync backups are happy and we just have a script to update
svn properties when .cvsignore files change.
If you drop the .cvsignore files from JikesRVM, we'll have
to track changes to the project subversion properties
in our backup scripts.

-bri