Add option to set COMPOSER_HOME

[mbrodala]

Instead of the fallback to HOME/.composer one can explicitly set COMPOSER_HOME. This should be an option.

I'm not sure about the best location though. Both composer::$home and composer::project::$home come into mind where the former actually makes more sense but would make it harder for composer::project to use.

Suggestions?

[igalic]

we could set the option in composer::home, and re-use it as default in composer::project

[mbrodala]

So you mean defaulting to $composer::home instead of $composer::params::home?

[igalic]

i'm starting to doubt the usfulness of composer::params.

generally, the hierarchy is:

composer::project::foo ← composer::foo ← composer::params::foo = 'bare constant'

however, composer::params, as a pattern, only makes sense if we're supposed to support (widely) different systems, where these params actually differ.

as it is, we can simplify this chain down to:

composer::project::foo ← composer::foo = 'bare constant'

[mbrodala]

Alright, I'll gladly go with this.

[igalic]

well, then, please prepare a pull request!

[mbrodala]

Apparently the current solution yields a warning in case $composer::home is not set:

Warning: Exec[composer-fix-permissions](provider=posix): Cannot understand environment setting "COMPOSER_HOME="

Gotta tweak this.

[igalic]

i think we should establish Pull Requests for everything, i was a bit confused about your push to master :O

(yes, that means i create pull requests for my pushes too.)

[mbrodala]

Yeah, usually going via PR should be preferred, especially to wait for Travis confirmation. But in this case I have tried it locally on a development setup to actually develop the fix. ;-)

[igalic]

nod