SVN or Git for repository with hierarchial access control

Question

Which one do you recommend for a commercial project with developers that need to have access to a particular part of repository only?

Development IDE is Eclipse

and Programming language is C/C++

Key features of the requirement is: Authoritative and ACL hierarchical access to repository

Answer 1

Git, combined with a "central" server managed with Gitolite, can provide all the fine-grained control you need (per user/per group, with access to all or only some part of the repo, even to only some branches).

That being said, if your developers are more familiar with a CVCS like SVN, it might be wiser to use that knowledge at least to start the project (and uses Authentication method in your apache server configuration): a CVCS can be quite different from a DVCS.
(plus you still can later convert a SVN repo into a Git one)

Answer 2

Git is much more modular and flexible than SVN. If some developers only need access to a part of the repository, you can make it a submodule (i.e. a independent repository which is aggregated by your main repository). It is much easier to grant access to a different repository than to a single directory inside a filesystem.

It is a common practice for APIs or plugins to be separated from the main repository. For more information, have a look there.

Last point, software like Gitolite (the one I use for my own projects) and Gitosis (the one we use at work) make the administration of git repositories very easy.