OT? Using SVN on a project and for engines


#1

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


#2

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

Tim.


#3

Installing via the -x flag… Ex:

Script/plugin install -x
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.

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

#4

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

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


#5

Also:


#6

cd <your_project>/vendor/plugins;
svn co http://opensvn.csie.org/rails_engines/engines/tags/rel_1.0.4
engines


#7

James A. wrote:

cd <your_project>/vendor/plugins;
svn co 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