[RFC] Extension Managment using Composer
Re: [RFC] Extension Managment using Composer
I've merged this with the existing topic. It answers your original point of not including an upload feature and details the intergration with titania.
Formerly known as Unknown Bliss
No unsolicited PMs please except for quotes.psoTFX wrote: I went with Olympus because as I said to the teams ... "It's been one hell of a hill to climb"
Re: [RFC] Extension Managment using Composer
Ok thanks, I have not noticed this was already suggested.
After reading the topic, I still dont understand why are you going to use Composer. Composer is great for developers, but why should it be used for installing Extensions? Why is not the simple upload form + "search and automatically download" feature enough? WP also has this and does not use Composer for it.
After reading the topic, I still dont understand why are you going to use Composer. Composer is great for developers, but why should it be used for installing Extensions? Why is not the simple upload form + "search and automatically download" feature enough? WP also has this and does not use Composer for it.
Re: [RFC] Extension Managment using Composer
WP don't use it because it was designed before hand - Drupal are moving to composer for their extensions/modules. Composer is much better at handling the transport and it handles dependency resolution in ways that are extremely complicated and it would be way too complicated to try and develop ourselves (I don't know of anyone who would argue with this).
I personally believe we should have an upload form but the transport/integration with titania should be done with composer - That's doing it properly.
I personally believe we should have an upload form but the transport/integration with titania should be done with composer - That's doing it properly.
Formerly known as Unknown Bliss
No unsolicited PMs please except for quotes.psoTFX wrote: I went with Olympus because as I said to the teams ... "It's been one hell of a hill to climb"
- EXreaction
- Registered User
- Posts: 1555
- Joined: Sat Sep 10, 2005 2:15 am
Re: [RFC] Extension Managment using Composer
Composer is used for handling downloads from remote locations as well as dependency management. For example, you could upload Ext 2 that requires Ext 1, then Composer would grab Ext 1 and install it as well when installing Ext 2.
- Master_Cylinder
- Registered User
- Posts: 361
- Joined: Wed Jul 31, 2013 9:54 pm
Re: [RFC] Extension Managment using Composer
Like the FreeBSD ports system...nice. I don't think they use Composer (I think it's mostly shell script and wget) for that but that is good functionality if it handles the dependencies.EXreaction wrote:Composer is used for handling downloads from remote locations as well as dependency management. For example, you could upload Ext 2 that requires Ext 1, then Composer would grab Ext 1 and install it as well when installing Ext 2.
These kids today...
Buy them books, send them to school and what do they do?
They eat the paste.
Buy them books, send them to school and what do they do?
They eat the paste.
Re: [RFC] Extension Managment using Composer
you need shell access to run
php composer.phar install
, since that's not available on shared hosting i see an issue.- DavidIQ
- Customisations Team Leader
- Posts: 1904
- Joined: Thu Mar 02, 2006 4:29 pm
- Location: Earth
- Contact:
Re: [RFC] Extension Managment using Composer
That is only needed for development. For the release this will be done and composer included in the download packages much like we do now with the nightly builds.