您如何在 IBM i 上组织 RPGLE 颠覆存储库？
您如何在 IBM i 上组织 RPGLE 颠覆存储库？
我目前在一家旅游商业公司工作，该公司拥有大量（大约 13k）的 RPGLE - 他们内部应用程序的源代码，最后他们希望使用版本控制并采用更现代的编码风格（整个 WDSC - RDi 的东西）。
所以我一直以来的项目就是一点一点地净化和现代化整个编码过程。
OS/400 的开源颠覆就像一个魅力，只有 2 个小功能安装过程中出现问题。
我脑子里对它应该如何运作有一个很好的印象，但我认为它打破了一些传统，所以我想听听你的意见。
/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
因此，主要区别在于没有不同的源文件，例如 QRPGLESRC、QCLSRC、QDDSSRC 等，而是一个包含所有项目源并且可以作为 WDSC 项目签出的源文件。 项目源文件也可以轻松地命名为“src”，就像在其他存储库中常见的那样，但如果某些开发人员想要将多个项目检出到 /QSYS.LIB/SOMELIB.LIB/ 中，他们不必担心命名空间本身。
所以你怎么看？ 是狂妄吗？ 你看到问题了吗？ 你已经有一些经验了吗？ 请分享！ :)
How do you organize your RPGLE subversion repository on IBM i ?
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).
So my all-the-time-project is to sanify and modernize the whole coding process bit by bit.
The open source subversion for OS/400 works like a charm with just 2 minor issues during install.
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.
/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
So the main difference would be not having different source files like QRPGLESRC, QCLSRC, QDDSSRC and the like and instead one 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.
So what do you think? is it hybris? do you see problems? Do you have already some experience? please share! :)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
目前源和对象是如何组织的？ 您是否想要设置 Subversion 以使用当前的库结构而不是创建这个新的 IFS 目录结构？
我建议使用对象类型（pgm、file、cmd、pnlgrp、sql 等）作为文件扩展名，而不是源文件类型（rpgle、clle、sql 等）。 xyz.rpgle 和 xyz.clle 源可能会发生冲突，因为它们都编译为 XYZ *PGM。
How are the source and objects currently organized? Would you want to set up Subversion to work with the current library structure instead of creating this new IFS directory structure?
I'd suggest using object types (pgm, file, cmd, pnlgrp, sql, etc.) for file extensions instead of source file types (rpgle, clle, sql, etc.). You could have xyz.rpgle and xyz.clle sources in conflict as they both compile to XYZ *PGM.