On Apr 1, 2007, at 16:14, Philippe Legay wrote:
> I have received a big projet (2000 files + 8000 gif files).
>
> My idea is :
> 1) tar zxvf bigproject.tgz
> 2) Then check-in check out the files that I will modify for bug
> correction.
>
> So is it or not possible (I read some time yes, some time no and I did
> succeed to do it) to create .cvsignore for the files of
> bigproject.tgz (except for the modified files) that allows me to do
> svn import or svn add without include files from the bigproject.
>
> If yes how must I do that (specific version of the server or the
> client ?) Must the name of .cvsignore file be .cvsignore or can it
> be "myexclusionfilelist" ?
>
> Who is responsable to manage the cvsignore file ? The client or the
> server ?
>
> Thanks for any clear pointer about this problem (that seems to be a
> classical one).
"cvsignore" is a feature of CVS. This is Subversion. It has similar
but different ways of handling the situation.
You have two places where you can tell Subversion that you would like
it to ignore things. One place is the global-ignores directive in
your client's config file (in ~/.subversion/config). This applies to
all working copies you might use on this client.
The other place is the svn:ignore property of every directory in the
repository. You can set svn:ignore of any particular directory, and
then commit that property change. Then all clients that use a working
copy containing that directory will obey those ignore settings for
that directory.
See the book:
http://svnbook.red-bean.com/en/1.2/
svn.advanced.props.html#svn.advanced.props.special.ignore
I didn't exactly understand your example with gzipping a tar file,
but if it is your intention to check that gzipped tar file into the
repository, I probably recommend you do not do that. Just check in
the individual files, uncompressed. It is difficult for Subversion to
construct reasonable deltas for compressed data, which means that if
you ever change what's in the compressed data, Subversion may have to
store the entire file in the repository again, rather than being able
to store just a small delta, as it would be able to do if the data
were uncompressed. You may save some space initially by checking in
compressed items, but the more you modify them over time, the more
those space savings will disappear, and then start taking even more
space than it would had you just gone with uncompressed data from the
beginning.
Of course with GIF files they're already internally compressed, so
they're already difficult for Subversion to diff efficiently.
If I've misunderstood the scenario, then by all means please elaborate.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Apr 1 23:36:47 2007