Hi,
Here are the results of my investigations. I use TortoiseSVN on Windows and there is a SCC Provider called TortoiseSVNSCC.
TortoiseSVNSCC Download Page
I have downloaded the install.reg (change the path to the location where you have installed the SCC Provider) and the newest Version.
Before I have installed the SCC, I also had installed the TortoiseSVN (the SCC need it). In the SCC Package there are some old files, so I have choosed only the files which don't come with the TortoiseSVN.
After that, I can choose the ToirtoiseSVNSCC in the VCS plugin. Now checkout a repository project into a local directory (working copy).
In the configuration window of the VCS plugin set the Local Path to the directory of the working copy and set the Aux Path to a Subversion Url.
Code:
svn+ssh://user@server/repository/project/trunk
The User and Project fields are empty!
If you click on "Okay", the Log Browser will be open. Close the browser and the VCS icons and menus are enabled.
Open the "VCS preferences" and set the following properties:
If you click with the right mousebutton on a package in the object browser of PLSQL-Dev, you can see an "Add to CVS" menu point. Click on that und the package will be open, but you get the following error:
But the package is saved to the working copy. Here is a problem within the SCC. You can click with the RMB into the open package source window and choose the menu entry "Add to VCS" again and the Tortoise Add Window comes up. You have successfully added the package file to the repository.
With the menu entry "Checkin" you can check one file into the repository, "Checkin files..." let you choose some files from a list. You have to select the files (!) from the list, don't click "Okay" without any selection. You will see now the Tortoise Commit Window and the file content is saved to the repository.
Sometimes you get, everytime you try to add a file to the repository, the error above. It seems, that the SCC lose the synchronisation to the working copy. I don't have a workaround at the moment for this "feature".
Another problem is, if the SCC is not synchron with the working copy, you can have some added files, which will never be commit to the repository. The SCC provider is file-based, so it commits only known files (which the SCC has added). It doesn't check the status of other files within the working copy.
~witchi