So, it sounds like MKS Implementer is a source version control system as well as an integrated build system. That's not what SVN is. There is no doubt that I see the value in the combination, my point is just to keep SVN what it is and not add on other things that make it IBMi specific.
-Jim
Jim Steil
VP of Information Technology
Quality Liquid Feeds, Inc.
608.935.2345 office
608.341.9896 cell
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Friday, May 14, 2010 2:34 PM
To: Midrange Systems Technical Discussion
Subject: Re: Subversion and RPG source change management
jim@xxxxxxx wrote:
I don't mean to be disrespectful, but why would you want to store
info on how to create the object? Isn't that outside the scope of a
version control system? What am I missing?
<vendor mode=on>
In the IBM i world, objects have very special (and unique) characteristics that are critical. Object ownership, authority adoption, etc.
A simple source management system (especially one that's not designed for IBM i) has no concept of these things.
Most modern IBM i change control systems (like MKS Implementer) has the ability to recreate an object based on it's original attributes.
Additionally, they have the ability to retain data in physical files that are being promoted, recompile related programs when promoting a physical or logical file, etc.
</vendor>
david
(who works for MKS, on the Implementer product, in addition to running midrange.com)
--
IBM i on Power Systems - For when you can't afford to be out of business
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
