On Tue, Jul 2, 2013 at 7:22 PM, Daniel Friesen
<daniel(a)nadir-seen-fire.com>wrote;wrote:
Another one is extension assets. Have you dealt with
the fact that MW
doesn't have a proper path to serve the css/js in debug mode, images to IE,
and other assets that an extension needs.
Installing to custom locations is trivial. And if we were to move to a full
Composer setup, we'd likely have a custom installer script for MW
extensions (which composer has support for).
I do not consider this a case of NIH. Composer is NOT an attempt by the PHP
community to provide a way to mange their own plugins.
Composer is an
attempt by the PHP community to let PHP applications and libraries depend
and install 3rd party libraries that they directly need.
This is probably the more important point. Even Composer's own
documentation makes it pretty clear that composer is *not* a package
manager. We should be using composer solely for dependency management.
The main issue, though, that I was hoping Composer could solve, was not
extension installation but extension dependencies. For example, if there
are two or more extensions that require the same dependencies, have only
one copy of the 3rd party libraries across all of them. And that is exactly
what Composer was made to do, but achieving this is difficult considering
extensions are separate projects.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
www.whizkidztech.com | tylerromeo(a)gmail.com