...and ARCH and OS would be defined where?
This sort of thing may be better managed by your build process than
by the versioning system.
-wsv
On Mar 22, 2005, at 2:19 PM, Izzo, Tony wrote:
> I guess you could call this a feature request. What I'm looking at
> specifically is a Subversion repository that I'm using to manage a
> multi-platform project that incorporates third-party binary code,
> which I am storing in the repository using the scheme described in the
> excellent "Pragmatic Version Control Using Subversion". Now, the
> binary code I am using will eventually be shared among several
> projects, and therefore it is an excellent candidate to be managed
> using the svn:externals property. However, since we're talking about
> a multi-platform project, the URL to the external projects to be
> pulled when I check out my main project is platform dependent.
>
> For example, my project uses the SQLite database. The Solaris
> binaries for sqlite are stored in
> http://repository/vendor/sqlite/trunk/sparc-sol7/. The Windows
> binaries are stored in
> http://repository/vendor/sqlite/trunk/i586-Win32/.
>
> Therefore, in order to effectively use the svn:externals property in
> this environment, I would have to be able to specify a URL that varies
> with the platform on which the checkout is being performed. IE, I
> would have to be able to set my svn:externals property to something
> like "http://repository/vendor/sqlite/trunk/$(ARCH)-$(OS)/", with ARCH
> and OS being variables that are substituted at checkout time. Thanks.
>
> Tony
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
- application/pkcs7-signature attachment: smime.p7s
Received on Wed Mar 23 20:16:35 2005