Re: Subversion and RPG source change management -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

This structure looks okay, it is all in one repository. You were
first talking about different repositories, and if you would create
different repositories each repository will start numbering revision with 1.

Regards,
-Arco
2010/5/22 Richard Schoen <richard@xxxxxxxxxxxxxxx>

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.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.