SVN:只向用户显示 svn 树的特定部分
我有一个单个 svn 存储库,用于所有我的项目。在 svn 中,我还有一个目录,其中包含项目直接引用的编译库(如 .dll、.swc)。
我想要另一个开发人员为我做一个项目,但我不想向他开放我的整个 svn 树。如果只是无法提交,我只需在 authz 中设置读取权限,但我不希望他看到我所有其他源代码。
我不希望他进行两次签出,一次针对项目,一次针对库文件夹,因为如果我尝试签出并编译它,所有相对路径都会变得混乱。
因此需要以下内容:此用户签出主干应导致签出包含所有与此用户相关目录的文件夹结构,省略所有非-相关。
IE: 如果我的 svn svn checkout 看起来像这样:
-trunk
|-BinLibrary
|-Project 1
|-Project 2
|-ExternalProjects
|-Project 3
我希望他的 checkout 看起来像这样:
-trunk
|-BinLibrary
|-ExternalProjects
|-Project 3
这可能吗? 如果是:如何?
任何帮助表示赞赏!
编辑:我在Windows环境中使用svnserve(没有apache)
I have a single svn repository for all my projects. In svn I also have a directory which contains the compiled libraries (like .dll, .swc) which are directly referenced by the projects.
I want another developer to do a project for me and I don't want to open up my whole svn tree to him. If it was only about not being able to commit I would just set the read permission in authz, but I don't want that he see's all my other sourcecode.
I don't want him to make two checkouts, one for the project and one for the library folder, because all relative paths would be messed up if I try to check it out and compile it.
So want following: A checkout of trunk by this user should lead to a checkout that contains the folder structure of all to this user relevant directories, omitting all non-relevant.
I.e.:
If my svn svn checkout looks like this:
-trunk
|-BinLibrary
|-Project 1
|-Project 2
|-ExternalProjects
|-Project 3
I want his checkout to look like this:
-trunk
|-BinLibrary
|-ExternalProjects
|-Project 3
Is that possible?
If yes: How?
Any help is appreciated!
Edit: I'm using svnserve in a Windows environment (no apache)
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
在 authz 文件的
username =permission
行中,将权限留空意味着相应的用户没有访问权限,甚至无法读取。 在手册中,考虑以下示例:harry 无法阅读秘密。
您可以授予其他用户对整个存储库没有权限,然后对特定路径进行读写。
In the authz file, in the
username = permission
lines, leaving permission empty means that the respective user has no access, not even read. In the manual, consider this example:harry cannot read secret.
You can give other user no permission on the entire repository, and then on the specific path read-write.
也许可以尝试一下:
Per目录访问控制
Maybe give this a go:
Per Directory Access Control