Jules,
the deepest level of access control in subversion is "per-directory"
(unfortunately, IMHO).
But perhaps you might consider to move the file(s) in question to
".../include/hidden" instead of ".../include" and deny access to
"hidden" for all those who should not be able to checkout/export it from
your repository. Although this strategy would impose the drawback of
having to add ".../include/hidden" to your $INCLUDE path it should be
worth a try.
The only thing I can't tell for sure is how a checkout/export behaves
when stumbling over a non-accessible directory (does it cancel the
checkout/export or simply "ignore" that one?).
Best regards,
Thomas
> -----Original Message-----
> From: Jules Colding [mailto:colding@omesc.com]
> Sent: Monday, June 04, 2007 1:11 PM
> To: users@subversion.tigris.org
> Subject: Per-file access control?
>
> Hi,
>
> I'm in the process of migrating to subversion, but I have a
> nagging problem with one of my files.
>
> The file in question is a header from msdn that I'm not
> legally allowed to redistribute although anyone can get it
> from msdn by themselves.
>
> It would be annoying to be forced to distribute this file
> manually to my colleagues.
>
> So, is it possible to enforce per-file access control in svn
> so that some (when authenticated using ssh) will get the file
> when checking out but others not?
>
>
> Thanks,
> jules
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
GO Engineering GmbH - Stolzenbergstr. 13/IV - 76532 Baden-Baden
Geschäftsführer:
Helmut Gerstner, Dipl.-Ing. (FH)
Ralf Wörner, Dipl.-Ing. (FH)
Registergericht: Mannheim HRB 201811
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 4 15:49:26 2007