Download the PHP package wp-php-toolkit/svn without Composer

On this page you can find all versions of the php package wp-php-toolkit/svn. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of wp-php-toolkit/svn

Informations about the package svn

slug: svn title: Svn install: wp-php-toolkit/svn

see_also:

A Subversion client in pure PHP. Check out, update, and commit to SVN repositories – including WordPress.org's – over both svn:// and http(s)://, without the svn binary or any PHP extension.

Why this exists

WordPress itself lives in Subversion: core development happens in develop.svn.wordpress.org and every plugin and theme ships through plugins.svn.wordpress.org and themes.svn.wordpress.org. Automating anything around that ecosystem – deploying a plugin release, mirroring core, building developer tooling – traditionally requires shelling out to the svn binary, which hosted environments rarely provide.

This component implements the client side of both Subversion protocols in PHP: the custom svn:// wire protocol (ra_svn) and the HTTP-based one (mod_dav_svn, HTTP protocol v2). Checkouts and updates stream the server's "editor drive" – the same tree-delta mechanism the official client uses – so a full wordpress-develop checkout arrives in a single HTTP response and runs in tens of megabytes of memory.

svn:externals definitions are honored: referenced repositories are checked out as nested working copies, updated alongside their parent, and skipped by status and commit – matching the official client's behavior.

One caveat: working copies use this component's own .svn metadata format (JSON plus a pristine store), not the SQLite database of the official client. The repositories themselves are fully interoperable – commits made here are indistinguishable from commits made with svn – but a working copy created by one client cannot be operated on by the other.

Check out a plugin from WordPress.org

Point checkout() at any repository URL. The revision, the depth, and svn:externals handling are controlled per call.

Make a commit

Edit files, schedule additions and deletions, commit. Locally modified files that changed upstream too are marked conflicted on update and refuse to commit until resolved().

Talk to a repository without a working copy

open_session() exposes the repository primitives both protocols share: list directories, fetch files and properties, inspect revisions, or commit a changeset built in memory.

Supported and not supported

Supported: checkout (any depth), update (with per-file conflict detection), status, add, delete, revert, resolved, commit (files, directories, and property changes), svn:externals (including ^/, ../, //, and / relative URLs, pinned revisions, and the pre-1.5 syntax), svn:eol-style translation, anonymous and password authentication (HTTP Basic over http(s), CRAM-MD5 over svn://).

Not supported (yet): file:// and svn+ssh:// URLs, locks, svn:keywords expansion, svn:special symlinks, merge tracking, mixed-depth sparse checkouts, and working copies shared with the official client. HTTP servers must run Subversion 1.7 or newer (HTTP protocol v2).

All versions of svn with dependencies

PHP Build Version
Package Version
Requires php Version >=7.2
wp-php-toolkit/bytestream Version ^0.10.1
wp-php-toolkit/filesystem Version ^0.10.1
wp-php-toolkit/http-client Version ^0.10.1
wp-php-toolkit/xml Version ^0.10.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package wp-php-toolkit/svn contains the following files

Loading the files please wait ...