On 26-Feb-08, at 9:26 AM, Reedick, Andrew wrote:
> Nope. What you’re asking for goes against Subversion’s design
> paradigm and/or philosophy.
>
> The server has no control over what the client asks for nor what
> the client does with the data it receives. You would need to
> modify both the client and the server to have some kind of
> authentication/validation in order to ensure that only “authorized”
> clients are used. Or you could require that people use custom
> checkout scripts, but you would need to audit your people’s
> computers to detect any other svn clients.
>
> Obligatory question: why would you want/need to force people to
> checkout entire branches?
The OP seems to be worried about people making mistakes. It sounds
like a problem better addressed by 1) providing checkout+build
scripts and/or 2) user education.
—Toby
>
>
> From: Merten, Alexander (External)
> [mailto:Alexander.Merten.External_at_eads.com]
> Sent: Tuesday, February 26, 2008 3:34 AM
> To: 'users_at_subversion.tigris.org'
> Subject: Restricting Check-Out Function
>
> Dear all,
>
> is it possible to restrict the checkout function of subversion, so
> that only complete branches can be checked out? We want to forbid,
> that people check-out single files or subfolders of a branch.
>
> Is this something that can be done server-side or is that something
> that can only be implemented by a client-side customization (e.g.
> by customizing TortoiseSVN)?
>
> Greetings,
> Alexander Merten
>
Received on 2008-02-26 17:08:31 CET