Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do you organize your RPGLE subversion repository on IBM i?
    primarykey
    data
    text
    <p>How do you organize your RPGLE subversion repository on IBM i ?</p> <p>I'm currently working in a travel business company that has a vast amount (about 13k) of RPGLE - sources for their in-house application and finally they want to use version control and adopt a more modern style of coding (the whole WDSC - RDi stuff). </p> <p>So my all-the-time-project is to sanify and modernize the whole coding process bit by bit. </p> <p>The <a href="http://www.softlanding.com/subversion/d-subversion.htm" rel="nofollow noreferrer">open source subversion for OS/400</a> works like a charm with just 2 minor issues during install.</p> <p>I have a pretty good image in my head how it should work, but i think it breaks with some traditions, so i want your opinion.</p> <pre><code>/subversion/repositories/{name of the in-house-application} /{project_a} /trunk /doc /sql /{a source file that is named like the project. i.e. project_a } /myRPGsrc.rpgle /myCLLEsrc.clle /myDDSsrc.dspf /myDDSsrc.pf /compile.clle .iseries_project_properties .project /branch /tag /{project_b} /global_stuff /nightly_build </code></pre> <p>So the main difference would be not having different source files like QRPGLESRC, QCLSRC, QDDSSRC and the like and instead <em>one</em> sourcefile that contains all project sources and can be checked out as an WDSC-project. The project-sourcefile could also easily be named "src" like it is common on other repos, but in case some developers would want to check out multiple projects into /QSYS.LIB/SOMELIB.LIB/ they wouldn't have to worry about namespaces themselves.</p> <p>So what do you think? is it hybris? do you see problems? Do you have already some experience? please share! :)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload