Rails - May 2006 - Do you store the source of third-parties plugins you rely on in your own version control ?

Hi!

well the subject is telling everything - I''m just curious to know how
other
railers handle this (for me the answer is yes, clearly!)

cheers

Thibaut
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060512/0b59b57b/attachment-0001.html

"Thibaut Barr?re" <thibaut.barrere@gmail.com>
writes:
> Hi!
>
> well the subject is telling everything - I''m just curious to know
how other
> railers handle this (for me the answer is yes, clearly!)
>
It depends, generally I just use svn:externals and point to their
repository, unless I think I need to modify their plugin, in which case I
store it in my version control. 

But while deploying the application, I use capistrano, which svn
exports everything and hence even the code of the plugin is also pulled in. 

HTH.

-- 
Surendra Singhi
http://ssinghi.kreeti.com, http://www.kreeti.com
Read my blog at: http://cuttingtheredtape.blogspot.com/
,----
| "O thou my friend! The prosperity of Crime is like unto the lightning,
| whose traitorous brilliancies embellish the atmosphere but for an
| instant, in order to hurl into death''s very depths the luckless one
| they have dazzled." -- Marquis de Sade
`----

I do. It makes sense - you want everything in the right place for 
deployment. I don''t want to have to collate my project before uploading
it... Of course, most of the time with rails web development
''source'' is
the same as deployed scripts... If I was using a compiled 3rd party 
plug-in of some kind, and I wasn''t altering the source, I
wouldn''t see
the need for bulking out my repository - until such a time as I had to 
make my own changes.