Phlip
1
Railsters:
The -x option sets your plugin up as an svn:external, to track updates
automatically.
I tried to remove a plugin, and got this:
$ svn rm naugty-plugin/ --force
D naughty-plugin/…
…
svn: ‘naughty-plugin’ is not under version control
That’s not a good sign. Then I svn ci my project, cap deploy it, and
the plugin (and its ill effects) are still on the server.
How to croak an svn:externalled plugin?
–
Phlip
http://c2.com/cgi/wiki?ZeekLand ← NOT a blog!!
Phlip
2
On 6-Mar-07, at 10:03 PM, Phlip wrote:
…
svn: ‘naughty-plugin’ is not under version control
That’s not a good sign. Then I svn ci my project, cap deploy it, and
the plugin (and its ill effects) are still on the server.
How to croak an svn:externalled plugin?
–
Phlip
http://c2.com/cgi/wiki?ZeekLand ← NOT a blog!!
Phillip, what does svn status tell you? Is the plugin listed as an
external, ala:
X vendor/plugins/naughty-plugin
if it doesn’t show up this way, then it’s not an external defined entry.
svn propedit svn:externals vendor/plugins
will allow you to edit the externals directly.
Is it possible that you ran svn remove from the project root? and not
svn remove vendor/plugins/naughty-plugin?
hopefully the above gets you further ahead. I’m hitting the hay now -
l8r.
Cheers,
Jodi
General Partner
The nNovation Group inc.
www.nnovation.ca/blog
Phlip
3
Jodi S. wrote:
X vendor/plugins/naughty-plugin
Yep.
svn propedit svn:externals vendor/plugins
will allow you to edit the externals directly.
Google for that, aaaand here’s the tip:
http://blog.opensourceconnections.com/2007/02/13/how-to-remove-plugins-installed-as-svnexternals/
The svn propedit svn:externals . --editor-cmd vi done it.
New question: Should that file contain this?
plugin ./script/plugin
I nuked it too, cap deploy, and the naughty-plugin didn’t follow me home
this time!
I been banging on my plugins too much, huh?!
–
Phlip
Redirecting... ← NOT a blog!!!
Phlip
4
On 6-Mar-07, at 10:50 PM, Phlip wrote:
Google for that, aaaand here’s the tip:
http://blog.opensourceconnections.com/2007/02/13/how-to-remove-
plugins-installed-as-svnexternals/
The svn propedit svn:externals . --editor-cmd vi done it.
New question: Should that file contain this?
plugin ./script/plugin
no it shouldn’t. ( I gather you ran that cmd from RAILS_ROOT? )
the format of the externals file is
directory external_path
for instance (all commands run from RAILS_ROOT)
imac:~/Documents/dev/zoop jodi$ svn propget svn:externals vendor/plugins
savage_beast http://svn.nnovation.ca/svn/savage_beast/trunk
means thtere’s a directory under vendor/plugins called ‘savage_beast’
that is externally linked to the url above.
one more note, you can use textmate to handled all svn propedits read:
http://macromates.com/textmate/manual/
using_textmate_from_terminal#the_general_editor_variable
cheers,
Jodi