On 1/11/11 4:42 PM, Tom Boutell 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.
Official answer: only use released sandboxes (aka PR4 as of today).
Everything else is for hackers and "aware" developers/hackers.
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
not a bug.
src/vendor/ contains a "minified" version of the third-party
dependencies (so that the archive is not too huge in size).
vendor/ is where you can put the "real" dependencies.
* 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.
exactly, that's the expected behavior (see above for the explanation).
* 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?
They are not fatal errors. You can mostly ignore them.
Fabien
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!
--
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
