Re: Basic source control for RPGLE/CLLE/DDS -- 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.

On 7/14/2016 5:02 AM, Paul Bailey wrote:

Do you use the
iProjects feature of RDi? I was hoping somebody would say that was worth
the effort of learning because it appears to copy sources to the i before
compile, but everywhere I've seen uses various scripts they maintain
themselves.

My learning curve for iProjects was measured in minutes. I don't
maintain any external scripts; I compile with a right click.

When you copy the source back to the i for compile, do you have to remember
to copy the /COPY books as well or do you keep a copy of the /COPY books on
the i at all times?

You'll need to copy /every/ bit of source that is required.

I'm reticent to leave source on the i because I don't
want colleagues to think "i'll just make a quick change here" and the
change gets lost because it didn't get back to the repository for
whatever reason.

What are your goals for implementing Git? More to the point, how do you
expect to implement those goals if you have colleagues who aren't on
board with using Git?

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.