build svn on VOS stratus system.

["Zhao, Jing" <Ji...@chasepaymentech.com>]

 We have VOS computer which was made by Stratus company. Our Subversion is running on Solaris system. To compile whole subversion on VOS system is not easy at all. Actually, we don't need whole subversion. We just need svn mini client on VOS system. Is there any way to just compile 'svn' and 'svnlook' without compiling svnadmin and svnserve to make it simple? Or either other work around way to checkout file from subversion? 

 Any comments or hints are really appreciated. 

 Jing  
  
Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com.
THIS MESSAGE IS CONFIDENTIAL.  This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above.  If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments.  If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: build svn on VOS stratus system.

[Dominic Anello <da...@danky.com>]

On 2006-08-18 14:43:31 -0400, Zhao, Jing wrote:
> 
>  We have VOS computer which was made by Stratus company. Our
> Subversion is running on Solaris system. To compile whole subversion
> on VOS system is not easy at all. Actually, we don't need whole
> subversion. We just need svn mini client on VOS system. Is there any
> way to just compile 'svn' and 'svnlook' without compiling svnadmin and
> svnserve to make it simple? Or either other work around way to
> checkout file from subversion? 
> 
>  Any comments or hints are really appreciated. 
> 
>  Jing  

You shouldn't need anything special to compile a minimal svn
configuration.  If libraries for optional features are missing they will
simply not be included.  The subversion configure script is pretty smart
about determining what it is OK to build.

Mimimal configuration requries (AFAIK)
* apr and apr-util
* expat (? may only be necessary for ra_dav)
* iconv (?)

Things you can leave out:
* openssl, neon - disables ra_dav repository access module (http,https) 
  support in svn
* apache - disables building mod_dav_svn (you need to supply --with-apxs
  to build this one anyway)
* bdb - disables fs_base for Berkeley DB repository in svnadmin
* python - only need if building from a fresh checkout, not necessary if
  building from tarball
* ruby, perl, java, swig - only necessary for optional bindings

This will give you an svn that supports only the svn://, svn+ssh://, and
file:// protocols and an svnadmin that only supports the fs_fs (file
based) repository filesystem.

As far as not building svnadmin and svnlook, AFAIK there is no way to
do that, but I believe they depend on exactly the same libraries as svn
and svn, so they shouldn't give you any additional trouble.

Good Luck!

-Dominic

-- 
I am the sound a balloon makes falling into the sky;
the sweat of a lump of ice in a summer river.