|
I was thinking 'make test' and 'make install'.
Setting authorities, object auditing, journals - all this and more happensin IBM i but not in an open source build like say, the Gimp, or PGP.
On 2/5/2016 11:55 AM, Aaron Bartell wrote:
internalSaying the right thing is hard. I envy you authors (in the good way)!
Funny you should say that. When I write articles I first have an
grammar smith fix it up and then the trade rag has their grammar smith'promote
formulate it to their mag's style. Those people make geeks sound so much
better than we are :-)
Git + make is a non-starter for me compared to Git + a home grown
to production' command.
Note that "make" isn't for promoting/deploying, it is for building.
I was thinking 'make test' and 'make install'.
Once
the project is built then the deploy can happen. There are tools to do
deploy but custom scripts/CL are fine also. I use tools and custom shell
scripts for open source stuff.
The central 'problem' as it were, is that no combination of open source
tooling is IBM i-aware. Deploying an RPG main program, its associated
*DSPF, the *SRVPGM it depends upon, the prototype source member that
other programs will eventually depend upon - all this is different to
copying files around which is what happens in PC land. Setting
authorities, object auditing, journals - all this and more happens in
IBM i but not in an open source build like say, the Gimp, or PGP.
Actually, having done a lot more shell
scripting this past year makes me realize shell scripting is what I had
always hoped CL would be.
I suspect that CL was always left very vanilla in order to encourage the
community and vendors to enhance it via 3rd party commands.
--
--buck
Visit wiki.midrange.com and register for an account. Edit a page that
helps you, and because it's public, you'll help someone else, too!
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
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.