What’s the right way to “freeze” a project once its been added to svn and is under version control? What happens is that freeze delets /vendor and the svn info in it. So the next time you run any svn commands, svn isn’t happy. Has anyone else gone through this? I’ve seen some similar sounding chatter online but nothing definitive.

Interesting.

I haven’t encountered that issue, in most of my situations I’ve already frozen rails and added plugins to my application before I’ve done the initial import or I don’t freeze rails because I know it’s going to a dedicated server (or VPS) where I have full control over the gems that are installed (yes, yes – I know – I’m not practicing what I preach when I do that)

I would assume an easy workaround (untested) would be to go ahead and remove the /vendor/rails directory yourself i.e.

rm -rf vendor/rails

svn remove vendor/rails

I’m assuming I have to re-freeze since I added the Chronic gem – correct? Else, I did the initial freeze before committing and everything have been good.

No – adding an external gem such as Chronic wouldn’t require you to re-freeze Rails.

A frozen rails will live in /vendor/rails
Plugins will exist in /vendor/plugins

As for freezing gems to your application – it depends on which method you’re using ( I linked to a few the other day) but if you’re using Geoffery Grosenbachs rake task – it freezes gems to the /lib directory IIRC