Re:Abandon your DVCS and return to sanity
by structural on Tuesday March 03, 2015 @02:00PM
(#9139786)
If particular frameworks want to tie themselves to a single server/host, that's their problem, and is specifically not a problem with any of Github, git or DVCSes generally.
You really cannot stop all people from being idiots all of the time.
That's not a hard dependency, it's a sensible default that you should be overriding if you're running composer install as part of your deployment process instead of including composer's vendor directory in your repo. Documentation: https://getcomposer.org/doc/05-repositories.md
Practically all packages use git sources. Yes, you can vendor them - congratulations, you just kicked the can down the road and moved the issue to the build step. The issue exists for other languages as well - maven/mavencentral, ruby/rubygems.org - but only composer depends on github very much. I don't like that but it's not like the other solutions are much better.
Re:Abandon your DVCS and return to sanity
by mercurial on Tuesday March 03, 2015 @03:08PM
(#9140341)
Many companies mirror maven, so having mavencentral go down is not a big issue. Does composer make it possible to deploy a mirror of its dependencies?
Yes, certainly: https://getcomposer.org/doc/articles/handling-private-packag...
You can use your own repository, so at least in theory that should be possible. I haven't done that in practice, so I can't comment any further.
If you happen to have - god forbid - a php app that pulls dependencies via composer you have a hard dependency on github since composer pulls practically all code from GH. I don't consider that a good idea, but that's how it currently is. [No, I don't do php and only sometimes have to clean up the resulting fallout]