Yep, probably needs some additional granularity.
CPYTOSTMF will auto-strip source lines when it's copying a source
member. Nice !! :-)
That will save Aaron a source copy program, although I'm thinking the
source info such as Desc/Type might need to be placed into the source
member as a header and stripped out on restore from SVN.
Regards,
Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 898-3038
Fax: (952) 898-1781
Toll Free: (888) RJSSOFT
-----Original Message-----
----------------------------------------------------------------------
message: 1
date: Fri, 30 Nov 2007 09:09:37 -0500
from: Adam Glauser <adamglauser@xxxxxxxxxxxx>
subject: Re: Automate source code backup to SVN
Richard Schoen wrote:
2.) Command might be:
SVNSYNC
File(DEVLIB/QCLSRC)
IFSProjectFolder(/devlib/qclsrc)
Include(*ALL/*CHANGED)
ChangeInt(*TODAY-mm/dd/yyyy)
I really like the idea of having a command to do this. I've been
rolling around the idea of something like this (without getting very
far) for a while. Having a i5/OS command line svn client would be a
huge leap for the ability of shops to start using svn, because it would
help the more green-screen oriented to be comfortable with the process.
Maybe it could even be integrated with PDM!
So I guess SVNSYNC would do something like:
a) svn (checkout||update) svn://<server>/<IFSProjectFolder>
<IFSProjectFolder>
... since the directory must be a valid working directory for the
commit to happen
b) for each [changed] member
CPYTOSTMF <file>,<member> -> <IFSProjectFolder>
end
c) svn commit <IFSProjectFolder>
<Then whatever RPG/Java code runs>
3.) CPYTOSTMF would be easier than reading the source with RPG. Less
programing :-)
Can CPYTOSTMF strip the date area and sequence numbers automatically? I
think that stripping these out will be necessary to avoid clutter when
viewing the revision history of a source member.
midrange.com
