After Derek's response and studying autoloading and phpunit bootstrapping and such (especially what FOSUserBundle does), I'm thinking my WIP patch should be canceled. Thoughts?
Also--and these are just assumptions I'm making from tidbits I've read on blogs, forums, and IRC--bin/vendors looks like mainly a convenience around some git submodules, and composer will instead be used to solve most package management issues in the future. For future reference, pull request for this WIP patch is: https://github.com/symfony/symfony-standard/pull/232 Problematic (Derek Stobbe) added a comment 5 days ago: > I'm -1 on this; I feel like bin/vendors should never contain user > modifications, and so I WANT any changes that have crept in to be > blown away. Any time I've been tempted to write hacky code as a > shortcut, this deters me and forces me to find a cleaner way to > handle things :) > > In development, I usually point the autoloader to a local path on > my machine where I'm making changes (you can even pass it an array > if you have some production bundles and some in development within > the same namespace, though you have to be careful with this > because odd things can and do happen). Then I can easily isolate > my work (into a new Netbeans project, for example), commit at > will, and not be at risk of losing work from a rogue php > bin/vendors install call.
signature.asc
Description: OpenPGP digital signature
