|
Hi guys, we are playing around with symfony2 currently, they use composer for dependency management (http://getcomposer.org). Composer makes it easy to manage dependencies through one single file in the shop base path and makes updating parts or the complete application a breeze. If the Oxid development team would provide a composer file the shop could be managed using composer - but this would take some effort. If the whole "Oxid Universe" would follow this paradigma a shop update would be as easy as modifing the composer file and running: php composer.phar update Or if one wanted to only upgrade the core something like php composer.phar update oxid/eshop Same goes for modules that support this way of updating. This would take out the "update hell" most of the developers are facing right now. I know this is just a rough idea, I just wanted to hear your opinion about using a package managment like this to keep updates and dependencies simple. --
best Alexander Kludt  __________________________ Phone: 09283-5925453 Fax: 09283-592671 Skype: kingschnulli Email: [email protected] Website: www.aggrosoft.de __________________________ Aggrosoft it intelligence GbR Tannstrasse 12 95111 Rehau GERMANY Sitz Rehau, Amtsgericht Hof Steuernummer: 223/165/54508 Ust.-Id. Nr. gemäß § 27 a Umsatzsteuergesetz: DE260722773 ___________________________ Diese Nachricht ist nur für den Empfänger () bestimmt, sollten Sie nicht der Empfänger sein löschen Sie diese Nachricht umgehend und geben Sie uns bitte per Email ([email protected]) Bescheid über den fälschlichen Erhalt. |
_______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
