Re: Subversion and RPG source change management

The beauty of SVN is either method will work nicely depending on how you
want to structure your repositories.

Actually I'm not sure what you mean with the versioning comment.

From my understanding Subversion auto-numbers versions no matter what so

I'm not sure what would become inconsistent.

The most important information for tracking a library version would be
to tag the version in the repository as you hit a release point.

Not sure if you saw my source tree example, but it's somewhat like this
and actually we may be saying the same thing in regards to structure.

Repository - iSeriesSource
SVN_QGPL
trunk
QCLSRC
QRPGLESRC
Etc.
tags
SVN_LIBRARYA
trunk
QCLSRC
QRPGLESRC
Etc.
tags
branches
SVN_LIBRARYB
trunk
QCLSRC
QRPGLESRC
Etc.
tags
branches

I would probably have a single top level repository with subdirectories
for each library and each source file within so I can rebuild a library
structure from the repo.

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
--------------------------------------------------------------------
I should have read through all mail first before commenting.... I
apologize
for saying you go to a PDM only focus.

Why do you want to create a repository for each library? You can create
a
new tree in the repository trunk for every library you need, and just
synchronize that specific subtree with your working copy which is your
master copy.
If you create different repositories you will have to deal with
different
revision numbers and non-consistent tagging and versioning between your
libraries.
Regards,
-Arco