Okay, there are a few ways of inserting the svn part into your
workflow. As I don't know how much control you have over your linux
hosts, some of the alternatives may not be possible. I'm listing the
alternatives in (what I believe to be) the simplest work-flow for
1. Check-out svn repository on linux host, work with notepad++ via
For this, you'd create a samba share on the linux host, i.e in your
home directory. You'd then check out the svn code to that directory,
then you mount the samba share on your Windows computer. You can now
edit the files as if they were local on your computer.
When you have made changes that you're happy with, you would check-in
the svn code by issuing 'svn commit' in the directory you had checked
out the code into.
So, for example, if you choose the directory /home/yourusername/
backup_vmware/, the commands would be:
- Check-out svn code
svn checkout --username YOUR_USERNAME --password YOUR_PASSWORD
- Configure and mount the directory in your Windows computer
Guides are available on this, google for "samba mount windows" or
- Edit and save files with notepad++
- Look at the differences in your code and the one in the svn
- If you're happy with the changes, check in the code to the svn
svn ci -m "Describe your commit here"
2. Check out svn repository on linux host, work with WinSCP
Essentially the same as above, just without the samba part. Basic
- Check-out the repository on the linux host
- Transfer the files from the linux host to your windows computer
- Make edits and save
- Transfer back the changed files to the linux host (to the directory
where you checked out the repository)
- Issue 'svn diff' to verify that you're happy with the changes
- Issue 'svn ci -m "Message"' to commit the changes
3. Check out the svn repository on your windows machine, transfer
files with WinSCP
Like number 2, only that you keep the repository on your windows
machine. This gives you a graphical interface to svn, which you may
As for revision numbering, svn takes care of that. The good thing is,
all the earlier revisions are available! Even if you delete a file in
r5, it's still available in r4 and can be checked-out.
When you want to create a release zip file, you simply zip up the
revision you like, and put it in the download area.
Talking about the older files, is hardaur still active in developing
the script? If no, do you have the correct permissions to move his
files around? All of the previous revisions are still available, so
even if you delete his files it would be possible to get them by
checking out an earlier revision.
Hope this helps!
Please get back to me if you have more questions!
Best regards, Pär
> Da: Par_Tojkander <par.tojkan...@gmail.com