On 6 September 2016 08:17:20 BST, Tony Marston <tonymars...@hotmail.com> wrote: >>I do NOT want the replacement PEAR library to update itself in the >>> background. >> >>Composer doesn't do that. > >Then how come I've seen several complaints in various forums about >composer >updating libraries in the background and screwing things up.
I would imagine for the same reason Stack Overflow is full of questions about their JS loop not running their PHP properly, or "resource expected, boolean found" errors: they don't understand what they're doing, or haven't read the manual properly. Composer updates your libraries when you run "composer update", or fetches the latest that you've said are valid if you run "composer install" and don't have a lock file listing which versions you last updated to (i.e. you deleted it or didn't commit it to version control). It updates *itself* if you run "composer self-update". And that's it, as far as I know; I'm not even sure what it would mean for it to do stuff "in the background", because (much like pear) it's just an admin tool, not something you include at runtime. Regards, -- Rowan Collins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
