Integrate option to create project

[mbrodala]

A new option, e.g. source => '<vendor>/<package>:<version>' could be integrated to allow executing composer create-project <vendor>/<package>:<version> <target>.

Example of the suggested configuration:

composer::project { $repository:
  ensure => present,
  source => 'typo3/cms-base-distribution:~6.2'
  target => $path,
  dev    => true,
}

This would execute composer create-project typo3/cms-base-distribution:~6.2 . in $path. Notice the trailing dot to ensure creation in the current execution path.

[igalic]

What's $repository in that case?

[mbrodala]

Oh sorry, it's just a title like typo3.

[igalic]

reviewing this, it would appear that composer::project should actually be composer::install (or perhaps a type composer_install)

composer::create_project could be a separate defined type.

[mbrodala]

The reason why I suggest this for composer::project is being able to define something like mentioned above. On the very first run, this would invoke composer create-project which in turn triggers composer install to initially resolve all dependencies. On continuous runs this only invokes composer install (unless an update should be enforced).

This is why I think having this in one place has its merits.

Otherwise I'd need a fact/inline template to determine whether to define composer::install or composer::project.

[igalic]

nod

[igalic]

igalic@levix % composer create-project --help
Usage:
 create-project [-s|--stability="..."] [--prefer-source] [--prefer-dist] [--repository-url="..."] [--dev] [--no-dev] [--no-plugins] [--no-custom-installers] [--no-scripts] [--no-progress] [--keep-vcs] [--no-install] [package] [directory] [version]

Arguments:
 package                 Package name to be installed
 directory               Directory where the files should be created
 version                 Version, will default to latest

i'm thinking we should stick to package and add an optional version instead of source

even though our target diverts from composer's directory.

maybe we could add that option, and deprecate target…

[igalic]

@mbrodala with this now ^ it seems we have a fairly complete design.
would you like to attempt a patch?

[mbrodala]

The reasons why I think source is better suited are these:

1. In the puppet world basically everything that has a target option also offers a source option.
2. With source we can promote the shorthand syntax <package>:<version> (source) while package would leave people requesting a version option.

[igalic]

+1

[mbrodala]

Alright, I'll try to get this working and add a PR. Not sure if I can get around this year though.