You have to start somewhere, but you also need to know which way you are
going so that you don't do something that will make it hard to get to the
ultimate destination. I think it is fine to use SVN in this manner,
particularly if you are going to avoid SEU. Any may even have some build
tools that will help do the whole build form within WDSC or Eclipse.
Are you interested in joining our little development effort? Create a
source forge id and I will add you to the project.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
From: "Richard Schoen" <richard@xxxxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Date: 05/28/2010 09:09 AM
Subject: Re: Subversion and RPG source change managemen
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Just a couple of comments that may or may not play into your efforts:
1.) Personally we have abandoned the Softlanding SVN server port and
running SVN natively on the i. Speed is just not good enough for our
environment. The AIX one could be better but since we've already moved
our server to Windows, no reason to look back.
2.) I am focusing on the client aspect of SVN for iSeries with the
concept that the SVN Server and repositories can be anywhere. I don't
want to own or support any part of the SVN server itself.
3.) Dan and I had a meeting the other day and my thoughts may to change
my scope of initial deployment to exclude SEU as an editor. By focusing
on RDI as the initial editor of choice, the regular
checkout/checkin/editing to SVN can simply be handled from the PC. If
this works as expected I will simply build a CL driven process to do the
checkout/build on the iSeries and not store the permanent source there.
Since we're a software vendor and do product builds this would
accomplish our goal of source in SVN and being able to build product
from the iSeries natively. This would also minimize the overall effort
because the only time a source member would touch a source file would be
when we build it.
This may fly in the face of some of the comments I've read here in
regards to preserving line numbers and dates and object info, but from a
software vendor perspective it should work nicely to manage all of our
source projects using SVN. We are typically rebuilding our libraries for
each new release anyway so the only time the object info really matters
is when we build the product libraries.
More food for thought :-)
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: 7
date: Fri, 28 May 2010 13:47:45 +0200
from: Arco Simonse <arco400@xxxxxxxxx>
subject: Re: Subversion and RPG source change management
Well, to some extend the AIX version of the client part is working out
of
the box. I was able to perform the most important svn client commands
(didn't try all) and they all worked well on the standard IFS. But when
it
comes to the /QSYS.LIB/ filesystem there are blocks on the road (as
expected). There was no EBCDIC to UTF8 conversion done by the client, no
CR/LF handling, and the hidden .svn files and temp files for svn export
try
to build in the QSYS filesystem, which of course doesn't work.
For the server part, I did not test that quite well, because I wasn't
able
to get the Apache DAV config right. And besides that, there is already
something arranged for that by the Softlanding port, although this port
uses
an older 1.4.0 SVN version. Probably we can adopt from that to a newer
version.
Regards,
-Arco
midrange.com
