I have created two repositories on a debian server. One svn repo, dev, will contain files and code used by engineers at the company. The other repo, doc, will contain sales docs, quotes etc that is to be used by the management/sales staff.
Given that the two repos usage requirements are different and the users that will use them have different levels of computer skills I want to be able to apply different management styles to each repository.
One such example, and my current issue, is that I want the doc repo to have auto-props enabled to add
svn:needs-lock property to all files. This is a request from sales and management as they are not confident with using the SVN yet (thus they want to stick to a lock-modify-unlock versioing model).
However I don't want to apply these restrictions to the dev repository.
So through the TortoiseSVN client I am able to modify the subversion config file to enable auto-props etc.
But how can I manage these to repos that are on the same server and use the same client to satisfy this svn:needs-lock issue?
Is there are better way of approaching this concept of having two repos that need to have different levels of restrictions.
Note: we are a small company and have no IT admin as such. The engineers are required to administer the IT as a side task of normal work. So solutions need to be simple enough to not warrant constant maintenance.