repo restructure

[GoogleCodeExporter]

i think it would be easier (for users who use svn update) to move the plugins 
repo into rutorrent/plugins and provide a plugins.ini with everything disabled 
by default.

Original issue reported on code.google.com by chris2...@gmail.com on 7 Apr 2012 at 9:22

[GoogleCodeExporter]

May be. But if i change repo structure now, then i will receive a lot of 
letters like "What happens, i can't update from svn". 

Original comment by novik65 on 8 Apr 2012 at 6:38

• Changed state: WontFix

[GoogleCodeExporter]

that doesnt make sense.
people who are using svn undertand how to read svn commit messages which will 
explain the change, which in my opinion makes it even easier to update.

Original comment by chris2...@gmail.com on 8 Apr 2012 at 6:47

[GoogleCodeExporter]

what hes talking about is people who used to download plugins from the old 
repository.

They will go to the plugin directory and do svn up and it will no longer work.

a BETTER solution is to set it up like this yourself, for instance:

download the full trunk

rm -r trunk/rutorrent/plugins
mv trunk/plugins trunk/rutorrent

now when you do svn up, it will work as you like

Original comment by Wonslung@gmail.com on 9 Apr 2012 at 1:09

[GoogleCodeExporter]

that is not supported in subversion

example: $ svn up
Updating '.':
Skipped 'plugins' -- An obstructing working copy was found
At revision 2035.
Summary of conflicts:
  Skipped paths: 1

if you are using an old version of subversion you wont get this error. It was 
unintentional and fixed in the latest version. This is why im suggesting this 
change to the structure.

Original comment by chris2...@gmail.com on 9 Apr 2012 at 5:27

[GoogleCodeExporter]

1) Remove all from trunk/rutorrent/plugins (with .svn subdirectory)
2) Move all from trunk/plugins to from trunk/rutorrent/plugins (with .svn 
subdirectory)

Original comment by novik65 on 9 Apr 2012 at 9:52

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

you just rewrote exactly what wonslung wrote...
When your distro updates to a recent subversion you will understand why that is 
wrong

@novik: Yes do that locally and svn commit
i think google code supports modern version control systems now too...

Original comment by chris2...@gmail.com on 9 Apr 2012 at 2:25

[GoogleCodeExporter]

yah, he's right.   subverions 1.7 is quite annoying....They made a lot of 
changes and instead of having a ".svn" directory in each subdirectory, you only 
have it in one location now.....because of this you can't even download "trunk" 
and then move trunk/rutorrent/ somewhere, then later update it.  If you try to 
do this with the new subversion you get an error.

I wasn't aware of these changes in subversion, but it does pose an annoying 
issue

Original comment by Wonslung@gmail.com on 10 Apr 2012 at 5:19