Sisyphus repository
Last update: 28 may 2020 | SRPMs: 17560 | Visits: 18626959
en ru br
ALT Linux repos

Group :: Development/Other
RPM: git-make

 Main   Changelog   Spec   Patches   Sources   Download   Gear   Bugs and FR  Repocop 

Current version: 0.1.1-alt1
Build date: 6 may 2016, 14:24 ( 211.9 weeks ago )
Size: 8936 b

Home page:

License: GAGPLv3+
Summary: version control and merging of intended and automatically produced results

git-make is a tool that helps in "inductive" development of results.
(It's a small set of commands implemented on top of git and make.)

On one side, it's a way to get a nice output by manually refining raw
automatic output, without the need to re-do the manual refining for each
new revision of your sources (Git will merge your previous tweaks).

It goes like this. You hold sources in Git, then make an output
automatically (with a rule from Makefile), then tweak something in the
generated output (because the program that produced it wasn't perfect
or didn't perfectly match your wishes), and then on the next
development cycle edit your sources, and get a tweaked (merged) output
from the new revision.

For every branch with sources (say, master), two additional branches are used:

* master_/AUTO/goal to hold what was automatically generated for goal;
* master_/OUT/goal -- your tweaked, manually inspected version of the
output for goal, based on master_/AUTO/goal.

On the other side, it's a kind of test-driven development: you can start by
creating a small example result for "goal", accept it as a one
conforming to your intentions (technically: commit in the special Git
branch: master_/OUT/goal). Since then, this committed example can be
viewed as the expected result of a test. Then you extend the rules in
your sources, so that they produce a larger set of results (saved in
the special branch master_/AUTO/goal), and gradually review them (by
committing to master_/OUT/goal only the things you accept as good).

The diff between master_/AUTO/goal and master_/OUT/goal shows what
doesn't yet work as expected in the current revision of master. If
there is no diff, this means that your rules and the program that
generates the results are correct (i.e., perfectly match your intentions).

Current maintainer: Ivan Zakharyaschev

List of contributors

List of rpms provided by this srpm:

  • git-make
    design & coding: Vladimir Lettiev aka crux © 2004-2005, Andrew Avramenko aka liks © 2007-2008
    current maintainer: Michael Shigorin