public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

Fixes #1822 Update 02-libraries.md 

If username is unrelated, then I propose `username` rather than `composer` or `acme` to avoid confusion.
pull/1824/head
myqlarson 2013-04-24 20:49:19 +12:00
parent 035dbcc8ff
commit fe88dee982
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/02-libraries.md
View File

@ -122,7 +122,7 @@ the `.gitignore`.
Once you have a vcs repository (version control system, e.g. git) containing a Once you have a vcs repository (version control system, e.g. git) containing a
`composer.json` file, your library is already composer-installable. In this `composer.json` file, your library is already composer-installable. In this
example we will publish the `acme/hello-world` library on GitHub under example we will publish the `acme/hello-world` library on GitHub under
`github.com/acme/hello-world`. `github.com/username/hello-world`.
Now, To test installing the `acme/hello-world` package, we create a new Now, To test installing the `acme/hello-world` package, we create a new
project locally. We will call it `acme/blog`. This blog will depend on project locally. We will call it `acme/blog`. This blog will depend on
@ -150,7 +150,7 @@ We do this by adding a package repository specification to the blog's
"repositories": [ "repositories": [
{ {
"type": "vcs", "type": "vcs",
"url": "https://github.com/acme/hello-world" "url": "https://github.com/username/hello-world"
} }
], ],
"require": { "require": {