# OT? Using SVN on a project and for engines

**URL:** <https://www.ruby-forum.com/t/ot-using-svn-on-a-project-and-for-engines/52299>\
**Category:** Engines\
**Created:** [January 12, 2006, 5:31pm UTC](https://www.ruby-forum.com/t/ot-using-svn-on-a-project-and-for-engines/52299 "2006-01-12T17:31:51Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![klancaster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/f1d935/32.png) [@klancaster](https://www.ruby-forum.com/u/klancaster)\
**Post date:** [January 12, 2006, 5:31pm UTC](https://www.ruby-forum.com/t/ot-using-svn-on-a-project-and-for-engines/52299/1 "2006-01-12T17:31:51Z")

</div>

Apologies in advance if this seems a bit off topic, but this seemed like  
a starting point for this question.

I installed the engine plugin using the svn method described on the  
engines wiki. No problem doing so, and it seems a good idea. I then  
installed the login and user engines using the script/plugin install  
method, and after (quite a few!) hours got them working.

We use subversion to manage our application as a whole, so now I have an  
interesting issue. I need to insure that everyone is using the same  
version of all engines, but since I did the install using the external  
svn call, I can’t add the code to OUR svn repository (or more correctly,  
I don’t know how to do this!). On the surface, the answer might be “just  
have everyone set up their external calls the same way”, but that  
potentially becomes an issue of its own, esp. when/if we have to modify  
plugin code.

Any thoughts / pointers on how we might manage this issue?

TIA,  
Keith

---

<div class="post-metadata">

**Author:** ![klancaster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/f1d935/32.png) [@klancaster](https://www.ruby-forum.com/u/klancaster)\
**Post date:** [January 12, 2006, 6:07pm UTC](https://www.ruby-forum.com/t/ot-using-svn-on-a-project-and-for-engines/52299/2 "2006-01-12T18:07:46Z")

</div>

Keith L. wrote:

> We use subversion to manage our application as a whole, so now I have an  
> interesting issue. I need to insure that everyone is using the same  
> version of all engines, but since I did the install using the external  
> svn call, I can’t add the code to OUR svn repository (or more correctly,  
> I don’t know how to do this!). On the surface, the answer might be “just  
> have everyone set up their external calls the same way”, but that  
> potentially becomes an issue of its own, esp. when/if we have to modify  
> plugin code.

Just point your svn:externals property at the tag for the version you  
want everyone to have. ie:

engines [http://opensvn.csie.org/rails\_engines/engines/tags/rel\_1.0.4](http://opensvn.csie.org/rails_engines/engines/tags/rel_1.0.4)

Tim.

---

<div class="post-metadata">

**Author:** ![klancaster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/f1d935/32.png) [@klancaster](https://www.ruby-forum.com/u/klancaster)\
**Post date:** [January 12, 2006, 7:44pm UTC](https://www.ruby-forum.com/t/ot-using-svn-on-a-project-and-for-engines/52299/3 "2006-01-12T19:44:32Z")

</div>

Installing via the -x flag… Ex:

Script/plugin install -x  
[http://opensvn.csie.org/rails\_engines/engines/tags/rel\_1.0.4](http://opensvn.csie.org/rails_engines/engines/tags/rel_1.0.4)

Adds it automatically to your svn:externals property and will be updated  
automatically along with the rest of your working copy when you SVN up.

-Nb.

```auto
 Nathaniel S. H. Brown http://nshb.net

```

---

<div class="post-metadata">

**Author:** ![klancaster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/f1d935/32.png) [@klancaster](https://www.ruby-forum.com/u/klancaster)\
**Post date:** [January 23, 2006, 5:11am UTC](https://www.ruby-forum.com/t/ot-using-svn-on-a-project-and-for-engines/52299/4 "2006-01-23T05:11:25Z")

</div>

Nathaniel B. wrote:

> Installing via the -x flag… Ex:
> 
> Script/plugin install -x  
> [http://opensvn.csie.org/rails\_engines/engines/tags/rel\_1.0.4](http://opensvn.csie.org/rails_engines/engines/tags/rel_1.0.4)
> 
> Adds it automatically to your svn:externals property and will be updated  
> automatically along with the rest of your working copy when you SVN up.  
> Okay, but this gives me a directory called vendor/plugins/rel\_1.0.4 when  
> I really want vendor/plugins/engines - how can I sepecify the branch and  
> have the directory named correctly?

TIA,  
Scott

---

<div class="post-metadata">

**Author:** ![klancaster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/f1d935/32.png) [@klancaster](https://www.ruby-forum.com/u/klancaster)\
**Post date:** [January 23, 2006, 11:19am UTC](https://www.ruby-forum.com/t/ot-using-svn-on-a-project-and-for-engines/52299/5 "2006-01-23T11:19:25Z")

</div>

Also:

- replace rel\_1.0.4 with whatever version you want to use;

- you can track bugs to the current release by using the revision at  
[http://opensvn.csie.org/rails\_engines/engines/branches/rb\_1.0](http://opensvn.csie.org/rails_engines/engines/branches/rb_1.0)

- james

---

<div class="post-metadata">

**Author:** ![klancaster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/f1d935/32.png) [@klancaster](https://www.ruby-forum.com/u/klancaster)\
**Post date:** [January 23, 2006, 11:19am UTC](https://www.ruby-forum.com/t/ot-using-svn-on-a-project-and-for-engines/52299/6 "2006-01-23T11:19:22Z")

</div>

cd \<your\_project\>/vendor/plugins;  
svn co [http://opensvn.csie.org/rails\_engines/engines/tags/rel\_1.0.4](http://opensvn.csie.org/rails_engines/engines/tags/rel_1.0.4)  
engines

---

<div class="post-metadata">

**Author:** ![klancaster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/f1d935/32.png) [@klancaster](https://www.ruby-forum.com/u/klancaster)\
**Post date:** [January 23, 2006, 11:46am UTC](https://www.ruby-forum.com/t/ot-using-svn-on-a-project-and-for-engines/52299/7 "2006-01-23T11:46:03Z")

</div>

James A. wrote:

> cd \<your\_project\>/vendor/plugins;  
> svn co [http://opensvn.csie.org/rails\_engines/engines/tags/rel\_1.0.4](http://opensvn.csie.org/rails_engines/engines/tags/rel_1.0.4)  
> engines

Thanks for that. I wasn’t sure if I could do something like that or if  
the “plugin install” did something more.

Scott
