Update docs for fossil support

doc/00-intro.md

@@ -37,7 +37,7 @@ flags are also required, but when using the installer you will be warned about
 any incompatibilities.
 
 To install packages from sources instead of simple zip archives, you will need
-git, svn or hg depending on how the package is version-controlled.
+git, svn, fossil or hg depending on how the package is version-controlled.
 
 Composer is multi-platform and we strive to make it run equally well on Windows,
 Linux and OSX.

doc/02-libraries.md

@@ -57,7 +57,7 @@ available platform packages.
 ## Specifying the version
 
 When you publish your package on Packagist, it is able to infer the version
-from the VCS (git, svn, hg) information. This means you don't have to
+from the VCS (git, svn, hg, fossil) information. This means you don't have to
 explicitly declare it. Read [tags](#tags) and [branches](#branches) to see how
 version numbers are extracted from these.
 
@@ -183,8 +183,8 @@ available, see [Repositories](05-repositories.md).
 That's all. You can now install the dependencies by running Composer's
 [`install`](03-cli.md#install) command!
 
-**Recap:** Any git/svn/hg repository containing a `composer.json` can be added
-to your project by specifying the package repository and declaring the
+**Recap:** Any git/svn/hg/fossil repository containing a `composer.json` can be
+added to your project by specifying the package repository and declaring the
 dependency in the [`require`](04-schema.md#require) field.
 
 ## Publishing to packagist

doc/04-schema.md

@@ -702,7 +702,7 @@ The following repository types are supported:
   file is loaded using a PHP stream. You can set extra options on that stream
   using the `options` parameter.
 * **vcs:** The version control system repository can fetch packages from git,
-  svn and hg repositories.
+  svn, fossil and hg repositories.
 * **pear:** With this you can import any pear repository into your Composer
   project.
 * **package:** If you depend on a project that does not have any support for

doc/05-repositories.md

@@ -222,7 +222,7 @@ for more information.
 ### VCS
 
 VCS stands for version control system. This includes versioning systems like
-git, svn or hg. Composer has a repository type for installing packages from
+git, svn, fossil or hg. Composer has a repository type for installing packages from
 these systems.
 
 #### Loading a package from a VCS repository
@@ -300,6 +300,7 @@ The following are supported:
 * **Git:** [git-scm.com](https://git-scm.com)
 * **Subversion:** [subversion.apache.org](https://subversion.apache.org)
 * **Mercurial:** [mercurial.selenic.com](http://mercurial.selenic.com)
+* **Fossil**: [fossil-scm.org](https://www.fossil-scm.org/)
 
 To get packages from these systems you need to have their respective clients
 installed. That can be inconvenient. And for this reason there is special
@@ -311,8 +312,8 @@ VCS repository provides `dist`s for them that fetch the packages as zips.
 * **BitBucket:** [bitbucket.org](https://bitbucket.org) (Git and Mercurial)
 
 The VCS driver to be used is detected automatically based on the URL. However,
-should you need to specify one for whatever reason, you can use `git`, `svn` or
-`hg` as the repository type instead of `vcs`.
+should you need to specify one for whatever reason, you can use `fossil`, `git`, 
+`svn` or `hg` as the repository type instead of `vcs`.
 
 If you set the `no-api` key to `true` on a github repository it will clone the
 repository as it would with any other git repository instead of using the

doc/06-config.md

@@ -149,7 +149,7 @@ Defaults to `$cache-dir/files`. Stores the zip archives of packages.
 ## cache-repo-dir
 
 Defaults to `$cache-dir/repo`. Stores repository metadata for the `composer`
-type and the VCS repos of type `svn`, `github` and `bitbucket`.
+type and the VCS repos of type `svn`, `fossil`, `github` and `bitbucket`.
 
 ## cache-vcs-dir