AW: How best to use externals for handling sensitive vendor library?
From: Markus Schaber <m.schaber_at_codesys.com>
Date: Mon, 24 Mar 2014 13:06:34 +0000
Hi, David,
Von: David Aldrich [mailto:David.Aldrich_at_EMEA.NEC.COM]
> The project source code is stored in a dedicated svn repository. We have chosen not to store the vendor library with our source code because we don't want the hassle of maintaining svn permissions for the library across trunk and branches. So we just instruct the developers who need the library to unzip the library straight into the working copy. This is inelegant and I am looking for a better solution.
> I guess the obvious solution is to use a 'svn external' to retrieve the vendor library from another svn repo or project. We can then tighten the permissions on the vendor library svn project. But what would happen to developers of the main project if they couldn't access the vendor library? Would the external reference fail gracefully or would the checkout fail?
Each checkout and update will by itself complete, but return a non-zero error code and error messages due to the failed external reference.
> I would be grateful for suggestions on how best to handle this problem.
In my eyes, the obvious solution is to fetch the vendor library via the build scripts (in exactly those configurations which need it). If your build mechanism does not have integrated SVN support, you can just use "svn checkout / svn update" commands via shell, depending on whether the directory already exists or not.
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
E-Mail: m.schaber_at_codesys.com | Web: codesys.com | CODESYS store: store.codesys.com
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
|
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.