Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add extra to disable installers #67

Closed
shama opened this issue Apr 8, 2013 · 5 comments
Closed

Add extra to disable installers #67

shama opened this issue Apr 8, 2013 · 5 comments

Comments

@shama
Copy link
Contributor

shama commented Apr 8, 2013

Setting this extra would disable installers and install to the native vendor dir. Useful for users who have configured their framework to consume packages from the default dir (but the framework has not officially supported it).

Reference this topic: https://groups.google.com/forum/?fromgroups=#!topic/composer-dev/9JtvlkQ1DNE

Maybe installer-disable?

@schmunk42
Copy link
Contributor

What's about this?

"disabled-installers": "*"

"disabled-installers": ["YiiInstaller","ZendInstaller"]

@shama
Copy link
Contributor Author

shama commented Apr 8, 2013

Disabling installers for specific frameworks but not all implies the user is using at least two frameworks simultaneously. I'm not sure it's plausible that a user will be using two frameworks simultaneously and if they are, they should be fine using the default vendor directory.

@schmunk42
Copy link
Contributor

Was just an idea. btw: Using Yii and Zend together is a perfect use case ;)

@Seldaek
Copy link
Member

Seldaek commented Apr 9, 2013

@schmunk42 if you use Yii you might use Zend components as libraries but probably not Zend MVC stuff. And for the libs going in vendor/ is just fine.

@sbuzonas
Copy link

I use WordPress and Moodle in a project. I want to implement my own WordPress installer but leave the Moodle behavior as is. I think if there is an implementation for this, it should expose the functionality in the public api so other installers can leverage this. #211 is one of these particular scenarios.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants