Re: Fwd: [Console_Color] Composer support for Console_Color (#1)

I agree – also, there is a difference between the PEAR installer and PEAR libraries. At least we always wanted that. ;-) I'm personally not yet convinced that the PEAR-layer in composer is really solid and useful, but anyhow, I have no objections adding this. People can play with it and see if it's worthwhile. If anything, I'd like to wait until composer matures before we add composer.json files everywhere so we don't have to deal with the hassle of upgrading a JSON structure when stuff changes. And composer is still in a very early state. Besides, I also agree with Christian that this is not really urgent by any means. Because composer can use a SVN or GIT as a source too to install a package. Or use a zip/tar from GH as a dist source. Till -- till Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Wednesday, April 18, 2012 at 12:21 PM, Daniel O'Connor wrote: > Hi all, > A lot of you may already have seen this on github, but for those who > haven't I'd encourage you to take a look. Remember, play nice with those > Composer folks :) > > > > > ---------- Forwarded message ---------- > From: Christian Weiske < > reply+i-4162827-1c33031f501330c8a11187104d6626e5536fb1bf-365751@reply..github.com > (mailto:reply+i-4162827-1c33031f501330c8a11187104d6626e5536fb1bf-365751@reply.github.com) > > > > Date: Wed, Apr 18, 2012 at 1:42 PM > Subject: Re: [Console_Color] Composer support for Console_Color (#1) > To: Daniel O'Connor <daniel.oconnor@gmail.com (mailto:daniel.oconnor@gmail.com)> > > > Why should we do this? Apart from that, Composer has a PEAR compatibility > layer so PEAR packages don't need a composer.json file. > > --- > Reply to this email directly or view it on GitHub: > > https://github.com/pear/Console_Color/pull/1#issuecomment-5191514 > >