SVN Libraries

[Joerg W.]

According to the About Dialog of my installed version of TortoiseSVN, I use version:
TortoiseSVN 1.10.1, Build 28295 - 64 Bit , 2018/07/15 12:14:12

This is linked with and uses the Subversion version:
Subversion 1.10.2, -release

1. Is it possible, to integrate/use/call only the (GUI-less!?) Subversion libraries (which offer the plain features as exported functions) into an own commercial software (without having to install TortoiseSVN which integrates into the file explorer)?
2. If yes, do we need a licence for this?
3. If yes, is there a licence fee?
4. If yes, is it per sold copy of our commercial product, per year (or other time period) or once?

Thank you so much,

kind regards
Joerg W.

[Stefan]

On Wednesday, September 26, 2018 at 4:45:33 PM UTC+2, Jörg Weisbrod wrote:

According to the About Dialog of my installed version of TortoiseSVN, I use version:
TortoiseSVN 1.10.1, Build 28295 - 64 Bit , 2018/07/15 12:14:12

This is linked with and uses the Subversion version:
Subversion 1.10.2, -release

1. Is it possible, to integrate/use/call only the (GUI-less!?) Subversion libraries (which offer the plain features as exported functions) into an own commercial software (without having to install TortoiseSVN which integrates into the file explorer)?

Yes, that's possible. But not recommended. Because the svn dll we build for TSVN does not guarantee the order of the exported functions nor does it guarantee that the functions stay the same.

I would suggest you build your own svn dll(s). To do that, you can either look at our build sources or just use the build instructions of the svn project.

 

2. If yes, do we need a licence for this?

if you use the svn dll that comes with TSVN, you might have to follow the GPL.

If you build your own svn dll(s), then you don't need a license because svn is licensed under the Apache license.

 

3. If yes, is there a licence fee?

No.

 

[joergwe...@gmail.com]

> I would suggest you build your own svn dll(s). To do that, you can either look at our build sources or just use the build instructions of the svn project.

Thank you for this short, but however very positive message!

I tried to checkout the build sources of the svn, but got the following error message, which maybe appears by "courtesy" of the IT department of my company.

Checkout from https://svn.osdn.net/svnroot/svn/trunk, revision HEAD, Fully recursive, Externals included
Unable to connect to a repository at URL
'https://svn.osdn.net/svnroot/svn/trunk'
Access to '/svnroot/svn/trunk' forbidden

From your point of view, is there any mistake, I make?
Is the path wrong ?
I have to admit that I guessed it from the path to the TortoiseSVN repository, given (with the turtle image) at the end of the download page on your website referenced on TortoiseSVN's About dialog.

Can you help me with the path or an advice, please?
And/or: Where can I find the "build instructions of the svn project" you mentioned?

Thank you very much again!!

Kind regards
Joerg W.

[Stefan]

On Monday, October 8, 2018 at 3:32:15 PM UTC+2, Jörg Weisbrod wrote:

> I would suggest you build your own svn dll(s). To do that, you can either look at our build sources or just use the build instructions of the svn project.

Thank you for this short, but however very positive message!

I tried to checkout the build sources of the svn, but got the following error message, which maybe appears by "courtesy" of the IT department of my company.

Checkout from https://svn.osdn.net/svnroot/svn/trunk, revision HEAD, Fully recursive, Externals included
Unable to connect to a repository at URL
 'https://svn.osdn.net/svnroot/svn/trunk'
Access to '/svnroot/svn/trunk' forbidden

the subversion repo is hosted on the apache.org, not osdn.net.

http://subversion.apache.org/download.cgi

the repo URL is:

https://svn.apache.org/repos/asf/subversion/trunk

Stefan