[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:externals optionally checked out as read only

From: Blair Zajac <blair_at_orcaware.com>
Date: Fri, 21 Nov 2008 10:02:20 -0800

Alain Palamara wrote:
> Hi all,
>
> I read a lot of messages concerning read only working copy, but didn't
> find a clear answer to my problem. I will explain you my situation:
>
> - We are developping FPGAs and use SVN to keep our source code and
> projects.
> - We are a team of developpers sharing projects and source code.
> - We use the svn:externals to checkout our IPs (common source files)
> into the projects.
> - Until now everthing is perfect. The fact is the IPs are shared by
> many projects and shall be modified/corrected with care. So we
> decided that only few people can commit the IPs that must be
> validated across projects. As we recommend developpers to explicitly
> name the directory that refers to IPs in external repositories, we
> would like to have them read only in the working copy to reduce the
> risk a developper modifies an IP, generate the FPGA bit stream
> (equivalent to the executable) and commits the project.
> Because the IPs will not commited at the same time the project and
> because the developper probably don't have the right to commit the
> IP, we become in this in a situation where the commited project is
> corrupted (refers wrong IP source) and can not regenerate the FPGA
> after a checkout.
>
> Ok, I hope my explanation was clear ;)
>
> So my question is: Is there a way to checkout externals as read only?
>
> I can imagine a "post-checkout" or "post-update" hook, but it doesn't
> exist. Or a better way could be a flag in the svn:externals property
> that specify per external if it is read only or not. Something like:
> [-r<revision>] [-read-only] <repos-url> <ext_dir>
>
>
> Any plan to support this in the futur?

No, there's no plan to support such a feature.

The solution now is to ensure that only authorized developers can commit to the
URLs that the external refers to, so you'll want some per-directory access
control set up.

Regards,
Blair

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-21 19:02:55 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.