silverstripe-installer/composer.json at 345a32ec3eea9203e869cb22307868bfcd7b0c6a - silverstripe-installer - Gitea

tonyair/silverstripe-installer

mirror of https://github.com/silverstripe/silverstripe-installer synced 2024-06-21 20:19:25 +02:00

Ingo Schommer 345a32ec3e Remove require-dev section, composer doesn't handle it well

Any "composer require <module>" call will first call
a "composer update". This *automatically* includes dev requirements,
without providing a way to turn off this behaviour.
A workaround would be "composer require --no-update <module> && composer update --no-dev <module>",
but that drastically reduces the usefulness of the command
for our target audience (moderately technical devs).

In the end, the small faction of devs needing the dev dependencies
also know how to install them on their own. And having a local phpunit
build actually gets in the way more than it helps in case you have
it installed through PEAR already (can get really weird when using the
PEAR provided "phpunit" binary, but the autoloader finds the composer managed classes).

2013-05-07 10:51:47 +02:00

15 lines

322 B

JSON

Raw Blame History

 {
 	"name": "silverstripe/installer",
 	"description": "The SilverStripe Framework Installer",
 	"require": {
 		"php": ">=5.3.2",
 		"silverstripe/cms": "3.0.*@stable",
 		"silverstripe/framework": "3.0.*@stable",
 		"silverstripe-themes/simple": "*"
 	},
 	"config": {
 		"process-timeout": 600
 	},
 	"minimum-stability": "dev"
 }