Re: Subversion and RPG source change management

You are correct the IFS is really just a middle-ground staging area.

We are using non-iSeries SVN repositories so PASE is not required for
our scenario, but if you used an iSeries version of SVN the IFS is the
storage location for all repositories. We previously had SVN Server
running on iSeries and moved to Windows because it's 20x faster.

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

------------------------------

message: 4
date: Fri, 21 May 2010 12:47:48 -0700 (PDT)
from: Nathan Andelin <nandelin@xxxxxxxxx>
subject: Re: Subversion and RPG source change management

From: Pete Helgren
But, what if you were using something like Sourceforge to store the
project? I am trying to understand what role the IFS plays in this
scenario.

The IFS could play a role in the check-out, check-in procedures:

- copy pf-src members to IFS stream files
- check in IFS stream files to SVN
- and visa versa

Most SVN clients, like the one Aaron Bartell spoke of, can copy stream
files from/to an SVN repository. But they don't know now to work with
pf-src members. So the IFS might be used as a middle-ground staging
area.

You might use CL commands for check-in and check-out, where the commands
use CPYTOSTMF and CPYFRMSTMF, to put/get pf-src members into an IFS
staging area. Then transfer to/from SVN from there.

Does anyone have Subversion running under PASE? And using the Apache
server to support SVN clients? If so, then the IFS would likely be used
to store the repository.

-Nathan.