i recently commented in another thread on this topic. i have created a pull a while ago but that solves some typos, makes the output a bit clearer etc. but fabien had issues getting it to work.
however i did not solve the main issue which is that all of this should run off of a single manifest file to prevent things getting out of sync. there are some tools for this like MR whi can handle cloning and updating pretty much any (d)vcs from a single config. as such this solution would also not require fragile bridges contrary to just using git submodules. also i dont like the workflow when i actually want to commit upstream stuff with submodules. Lukas On 11.01.2011, at 16:42, Tom Boutell <[email protected]> wrote: > I'd like to update the vendor folder of a project which I cloned from > the Symfony 2.0 sandbox, and in general to be able to tell other users > how to do that so they are not orphaned with older versions of Symfony > 2.0 if they start learning with my project. > > There seem to be some problems with doing this: > > * The .gitignore folder in the root of the sandbox ignores vendor/, > which does not exist, rather than src/vendor/. That seems to be a bug > > * However if it did really ignore all of src/vendor, I realize that in > cloning the project I would not immediately get a symfony folder, etc. > That doesn't seem to be what people want either > > fatal: git checkout: updating paths is incompatible with switching branches. > Did you intend to checkout 'src/vendor/doctrine-common/2.0.0' which > can not be resolved as commit? > > * If I try to run the scripts in bin, such as install_vendors.sh, they > make a vendor folder as a subdir of the home folder, not src/vendor > unless I cd to src first. > > * The update_vendors.sh script in bin produced errors, perhaps because > my project was cloned and then pushed up to github in its own right: > > * So I cleaned out src/vendor and ran sh ../bin/install_vendors.sh from src. > > 'git status' shows lots of modified stuff in vendor... > > * And I guess that makes sense, because the way the sandbox really > works is that you are using these scripts to get the latest, and then > using 'git add' to update it all in the sandbox project... > > * So... these files are traced in both git projects (the > vendor/whatever project and the main sandbox) at once? > > * So the right way to update in the future is: > > cd src > > sh ../bin/update_vendors.sh > > Then add and commit normally? > > This gives me: > > Already up-to-date. > fatal: git checkout: branch v2.0.0 already exists > Switched to branch 'master' > Already up-to-date. > > (More of the same) > > Are those "fatal" errors OK in this context? > > I am pretty sure there are at least some bugs in the setup, so I'm > sending this one to devs. > > Thanks for any insight into the update process! > > -- > Tom Boutell > P'unk Avenue > 215 755 1330 > punkave.com > window.punkave.com > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
