You can read directives for SVN access either on SourceForge page or below on this page.
Read-only SVN Access
This project's SourceForge.net SVN repository can be checked out with the following instruction set.
svn co \ https://stlport.svn.sourceforge.net/svnroot/stlport/trunk/STLport \ STLportor 5.0 release branch (STLPORT_5_0):
svn co \ https://stlport.svn.sourceforge.net/svnroot/stlport/branches/STLPORT_5_0/STLport \ STLport-5.0or 5.1 release branch (STLPORT_5_1):
svn co \ https://stlport.svn.sourceforge.net/svnroot/stlport/branches/STLPORT_5_1/STLport \ STLport-5.1
Developer SVN Access
See documentation.
Branches
Now we have following active branches:
- Main trunk
- Current development
- STLPORT_5_0
- Bugfixes for STLport 5.0 (last release is STLport 5.0.3 here)
- STLPORT_5_1
- Bugfixes for STLport 5.1 (last release is STLport 5.1.5), the last 'stable' release
Other branches that are still present have historical meaning only and may be deleted. You may locate them in SVN https://stlport.svn.sourceforge.net/svnroot/stlport/branches/ancient
Branches, tasks, tags, etc. policy
Snapshots (tags) may be found in SVN https://stlport.svn.sourceforge.net/svnroot/stlport/tags. Snapshots not intended for modifications, but may be removed
I should describe here SVN policy and use-cases. But a bit later
Other issues
Other useful URLs in SVN repository
- Documentation
- https://stlport.svn.sourceforge.net/svnroot/stlport/trunk/htdocs
- Packages
- Point of view, how to build STLport packages; now only Debian now (mainly because I'm not satisfied by Debian's team package): https://stlport.svn.sourceforge.net/svnroot/stlport/trunk/packages
- Performance test suite
- https://stlport.svn.sourceforge.net/svnroot/stlport/trunk/perf