Martin Spott wrote:
> Aside from all these 'technical' implications, serving Scenery via SVN
> (or whichever revision management) has the striking appeal of allowing
> incremental updates to users' local Scenery without having to delay the
> respective changes to the next 'official' release cycle.
Shortly before the year turns over I managed to push updates to our
Scenery SVN service, beginning with the "Objects/" subtree as a start
(to check if my automated directory tree comparison/merge works
properly ....).
This posting is meant as a reminder to those of you who are creating
binary packages of FlightGear: Please consider the availability of the
"libsvn" SVN client library at least as a highly useful dependency.
If "libsvn" is available at build time, TerraSync will link against
this library, thus circumventing an external call to the "svn" command
at the users' site. On a Linux system like Debian it would be
sufficient to link the binary against the shared library and to add
"libsvn1" to FlightGear's package dependencies.
If you're building for a platform that typically does _not_ feature a
shared "libsvn", then please consider either linking the 'terrasync'
binary statically against this library or to ship the shared library
together with FlightGear.
Thanks,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
------------------------------------------------------------------------------
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
