If you are not familiar with Subversion, you may be better served by a graphical client. We do not maintain a list of such clients; instead, we recommend you do a Web search for Subversion GUI client. The repository acts as a single source of truth and — as a central storage — it contains the complete history of changes of the versioned data in form of revisions.
The working copy is your local and private workspace that you use to interact with the central Subversion repository. You use the working copy to modify the contents of your project and fetch changes committed by others. The working copy contains your project's data and looks and acts like a regular directory on your local file system, but with one major difference - the working copy tracks the status and changes of files and directories within.
You can think of the working copy as of a regular directory with version-control capabilities. A working copy has an administrative directory named. The administrative directory contains metadata necessary for Subversion to manage the version-control capabilities.
There can be as much working copies from the same repository or project as you want with any combination of local modifications. In case you want to import existing non-versioned data into an SVN repository, you should run the svn import command. Here is an example:. To begin making modifications to your project's data, you have to create a local copy of the versioned project.
You can use the command line svn client or any GUI-based client that you prefer. Your local copy of the project is called a working copy and you create it by issuing the svn checkout command. As a result, you will get a working copy of the trunk of a project called MyProject that resides in MyRepo repository. The working copy will be located in MyWorkingCopy directory on your computer. Note that instead of checking out the trunk, you can check out some branch or a tag assuming they already exist in the repository.
You can get the working copy of the whole repository MyRepo, too. Generally, speaking, Windows users should download. Users of all other operating systems should download. Looking for previous releases of Subversion? All Subversion releases are available for download from the Apache distribution archive. Except for our currently supported releases, distributions of Subversion found in the archives are not supported by the community.
Note: only the users we created will be able to log into our repositories because we used the Require valid-user parameter. Theoretically, we are at the stage when we can run Apache and test our Subversion.
Provide the username you created and the password, and press OK. You will see the following page:. Under Advanced , select Environment Variables.
This starts the server when you start up your system. You must register svnserve with the service manager. To register svnserve , run the following command:. After Subversion is installed, you must create a repository. The command-line utility called svnadmin is the primary tool for server-side administrative operations. Access to the repository is controlled by file permissions and the user referenced for accessing the repository through the SVN client.
Ensure that user and group permissions for all files in the new repository reflect the type of access control that you want to have over the repository contents. By default, anonymous, read-only access is enabled for a new repository. This means that anyone with SSH access, regardless of repository permissions settings, can check out repository files. Now that you have created a repository, you can use the Subversion client to perform standard operations against the new repository by using the following base URL:.
Refer to the Subversion documentation for information on how to configure other protocols. Although Subversion does not require any particular subdirectory structure within a repository, it is a good idea to follow an established convention, as this book does. The typical repository layout should resemble the following figure:. Development of the main code line occurs in the trunk directories.
When a release is made, the current trunk source is copied into the tags directory, to a tag corresponding to the release. Subversion copy operations are not expensive in terms of storage because the server tracks changes internally. In the preceding example, 3. A tag is important for future work that might be necessary for patch creation or bug-fix releases.
0コメント