gtgt Or The Life After

In 2000, I released the Gnu Tem­plate Gen­er­a­tion Tools, also known as gtgt. It instan­ti­ates a set of sources that were read­i­ly pre­pared for being devel­oped, com­piled, and installed with the GNU ‘Autoconf/Automake’ devel­op­ment envi­ron­ment. A few years lat­er they were passed — by new lan­guages, tech­niques, and tools. But now — in the con­text of TDOSCA — we could revive gtgt:

[ en | de ]

What it is:

gtgt — spo­ken: git­ty-git­ty — is a set of scripts, which ini­tial­ize a c/c++ project in a way, that it can direct­ly be man­aged by the GNU Auto­tools — although one can nev­er­the­less them under the terms of any oth­er open or closed source license. How do you use the tools is explained in the gtgt-FAQ, which is part of every gtgt pack­age. The Gnu Tem­plate Gen­er­a­tion Tools have been revi­tal­ized for enabling us to cre­ate test data, that — under the lead­er­ship of the Open Chain Too­long Work­ing Group — become part of a Test-Dri­ven Open Source Com­pli­ance Automa­tion.

Where you can get it:

gtgt can be down­loaded from Github — by cloning the repos­i­to­ry as usu­al­ly, by down­load­ing it as a zip file via the GitHub tools, or by down­load­ing it from the gtgt ‑release-branch.

How do you use it:

The usage of gtgt is described in an FAQ.

What you may do with gtgt:

gtgt is dis­trib­uted under the terms of the GPL‑3.0. But its out­put — the cre­at­ed code and the instan­ti­at­ed project direc­to­ry includ­ing some spe­cif­ic gtgt-scripts may be dis­trib­uted under any oth­er open- or closed-source-license. The out­put is not a deriv­a­tive work of gtgt, even if it has been derived from gtgt by c&p.

And in what way is this …

… part of the over­ar­ch­ing top­ic FOSS Com­pli­ance? For ful­fill­ing the require­ments of FOSS licens­es, we have to con­sid­er spe­cif­ic indi­vid­ual cas­es as well as side effects — for soft­ware, pic­tures, or doc­u­ments. We should unhide trends and write guide­lines. Above all, how­ev­er, we must dri­ve for­ward the automa­tion of license ful­fill­ment, make our licens­ing knowl­edge freely avail­able, cast it into small­er tools, and bring it into larg­er sys­tems: Because FOSS thrives on free­dom through license ful­fill­ment, large and small. That’s what also this arti­cle is about.

Leave a Comment

Your email address will not be published. Required fields are marked *

To top