Composer
I know we don't want to use Composer because some people won't have it installed and that's another thing we'd need to support. Instead of having the users run Composer commands, can we, as developers, use Composer to install third-party stuff and then distribute it?
Re: Composer
Reply #2 –
It's the first item in a Google search for "composer".
Re: Composer
Reply #6 –
FYI, if it helps, another project I follow use Composer for its development environment but builds a snapshot of the libraries into the release version for use on Shared Hosting. That could be a way to go, then, and you'd also encourage more people to use release versions (aka stable) on shared hosting which is what most people will have, rather than trying to use development nightlies.
Re: Composer
Reply #7 –
Why can't shared hosts use Composer? It uses a Phar which is just PHP. The only reason they wouldn't is because they are using an old version of PHP (< 5.3) and I thought the next version will require >= 5.3.
Re: Composer
Reply #12 –
I am trying to install Pimple via Composer in a branch. I want to commit Pimple but it seems that vendor files are ignored. Should I just unignore it, commit, then ignore changes again or is there another strategy that people are using to add to vendor? Is vendor not supposed to be used like that?
Re: Composer
Reply #14 –
I added it to composer.json and it doesn't get committed because /vendor/* is in .gitignore.