Package: infrae.subversion
This zc.buildout recipe will check out anumberof URLs into its
parts directory.  It won’t remove its parts directory if there are any
changes in the checkout, so it’s safe to work with that checkout for
development.This is an example buildout part that uses this recipe:[development-products]
recipe = infrae.subversion
urls =
    https://svn.plone.org/svn/collective/PDBDebugMode/trunk PDBDebugModeThis will maintain a working copy ofPDBDebugModein theparts/development-products/PDBDebugModedirectory (notin the
parts directory itself).  Thus, the recipe handles multiple URLs fine.You can select a different location withlocation, for instance:location = srcWill extractPDBDebugModeinsrc/PDBDebugModeinstead ofparts.If you havepysvninstalled on the computer, it will be used. This
implies better performances.UpdateBy default, when buildout update the part, ansvn upis done for
each link. However, when a revision number is specified like this:https://svn.infrae.com/buildout/infrae.subversion/trunk@27829The SVN link is skipped for update. If you want to prevent update for
all SVN link of the part even if they do not contain revision number,
you can add the following option:ignore_updates = trueExportWithpysvninstalled, you can specify:export = truein your buildout part to get an SVN export instead of an SVN checkout.VerificationBy default, your checkout are checked against local modification
before any uninstallation step. This can take time on large checkouts,
and you may don’t want it in some case (like when used on buildbot for
instance). To prevent this step, you can use this option:ignore_verification = trueAs well, when the recipe update it can emit some warnings because a
directory have been removed. You can suppress that warning with:no_warnings = trueThe verification will still be done, and the directory will be checked
out again to replace the missing one.EggsIf you set the optionas_eggsin your configuration file,
checkouted URLs will be registered as development eggs in your
buildout. This only work for non-recipe development eggs.WarningIf you add a new egg, this will trigger a new
uninstall-reinstall cycle. You may want to use that option to setup
eggs coming from SVN for production, but not for development.Exported VariablesIf you set:export_info = trueTwo variables will be exported by this recipe:revisionswhich gives for each URL the corresponding revision
number,updatedwhich gives a list of URLs which have been updated with
new code.Since values to these variables changes each time you run buildout
(revision number changes), this trigger an uninstall/reinstall of the
part. We recommand to activate it only if you need it.Is always exported a variablelocationto say where are done the
checkouts, and a variableeggswhich contains a list of
checkouted eggs.SampleFor an example buildout that uses this recipe, please see theSilva
buildout.As well, thedoctest filecan provide more sample.Latest versionThe latest version is available in aSubversion repository.Changes1.4.5 (2009-01-29)Fix an error when some path have been added to the checkout
path. [eric]Still eggify and export information on update when running as
non-newest mode. [sylvain]1.4.4 (2009-01-28)Add ano_warningsoptions which remove some warnings when
updating a part. [sylvain]1.4.3 (2009-01-21)Add a login callback for people using PySVN. This let users
authenticate to an unauthorized svn. Thanks to Martin Stadler
(martin at siarp.de) for this fix. [sylvain]1.4.2 (2009-01-05)Automatically ignore.pycand.pyofiles while checking for
modified/added/removed files. [sylvain]Fix bug so.svndirectory is really ignored when checking for
added paths in the checkout directory. [sylvain]1.4.1 (2008-10-31)Bug fix:Correct typo in README.txt. [sylvain]Ignore.svndirectory when checking for added ones at
uninstall. [sylvain]1.4 (2008-10-31)New features:Addedlocationoption that allows you to override the default
/parts/partname location. [reinout]Addedas_eggsoption that installs the checkouts as development
eggs. [reinout]Bug fix:Don’t export revisions information if you’re offline with Py. Py
tries to connect to the SVN repository to do a ‘svn info’. [sylvain]1.3.1Bug fix:don’t try to collect export information if you have a svn
export. [sylvain]path were exported instead of URLs in the Native
implementation. [sylvain]1.3Remove the restriction to py 0.9.0, now that py 0.9.2 is out and fix
problems on svn status with strange userid. [sylvain]Correct an error rendering. [sylvain]Export information only for top level svn URLs in the native
implementation, this used to inject information from svn:externals
links included in URL list. [sylvain]Add tests for export information feature. [tlotze]Correct URL in setup.py [sylvain].1.2Refactor code, performances should be better at uninstall with Py
implementation [sylvain].Look for the environment variableINFRAE_SUBVERSION_IMPLto
select which implementation to use. Possible values arePYSVN(default) andPY[sylvain].Uninstall only look at directory which have been created by the
recipe in the part. Other are just reported [sylvain].Export two new variables, ifexport_infois set to true:revisionsWhich is lines formatted:link current_revisionupdatedWhich is lines containing updated links.[sylvain].1.1Add theignore_verificationoption [sylvain].1.0Base version of the recipe.