Reputation: 1819
I work with a subversion repository for a "generic" package that is full of files that shouldn't be there (site-specific files, hacks, etc). I do not have access to change this, and I've been stonewalled when I ask about having it changed on my behalf; I'm now after a workaround.
Is it possible to exclude some files from being checked out (or being pulled out of the repository when updating), so that I can work with some semblance of a clean package?
These files are independent and are not being pulled in by the other "good" files, so there aren't any dependency problems in that regard.
(Please note this is not the usual "How do I stop files from being committed" question answered by svn:ignore. Sorry. :-) )
Upvotes: 0
Views: 220
Reputation: 224039
Let me get this straight:
Did I sum up this right?
If I did, then I see two possible reasons for your problem:
I don't think SVN has a way to fix the problems arising from either of these reasons. (FWIW, I agree with the other answers that it doesn't even have the means to work around them.) To fix this, you would, in the first case, need to have someone explain it to you. (If they won't, see #2.) In the second case, get another job. Soon.
Upvotes: 1