tup-gittup

I Use This!

Very Low Activity

Analyzed 1 day ago. based on code collected 1 day ago.

Project Summary

Tup is a file-based build system - it inputs a list of file changes and a directed acyclic graph (DAG), then processes the DAG to execute the appropriate commands required to update dependent files. The DAG is stored in an SQLite database. By default, the list of file changes is generated by scanning the filesystem. Alternatively, the list can be provided up front by running the included file monitor daemon. It might be possible to generate the list from an IDE as well. By providing the file change log up front and storing the dependencies in an efficient database structure, updates can be performed with very little overhead. The monitor daemon uses inotify, so it is currently linux only. The rest of tup could probably be pretty easily ported to other UNIX-y systems, as long as there is a

In a Nutshell, tup-gittup...

...
has had 2,929 commits made by 57 contributors
representing 279,411 lines of code
...
is mostly written in C
with a well-commented source code
...
has a well established, mature codebase
maintained by a small development team
with decreasing Y-O-Y commits
...
took an estimated 74 years of effort (COCOMO model)
starting with its first commit in February, 2008
ending with its most recent commit 9 months ago

Quick Reference

Project Links:

Homepage
Issue Trackers
Mailing Lists

Code Locations:

https://github.com/gittup/tup

Similar Projects:

Managers:

Become the first manager for tup-gittup

Licenses

GNU General Public License version 2

Permitted

Commercial Use

Modify

Distribute

Place Warranty

Forbidden

Sub-License

Hold Liable

Required

Distribute Original

Disclose Source

Include Copyright

State Changes

Include License

These details are provided for information only. No information here is legal advice and should not be used as such.

All Licenses

Project Security

Vulnerabilities per Version ( last 10 releases )

There are no reported vulnerabilities

Project Vulnerability Report

Security Confidence Index

Poor security track-record

Favorable security track-record

Vulnerability Exposure Index

Many reported vulnerabilities

Few reported vulnerabilities

About Project Vulnerability Report

Did You Know...

...
in 2016, 47% of companies did not have formal process in place to track OS code
...
by exploring contributors within projects, you can view details on every commit they have made to that project
...
use of OSS increased in 65% of companies in 2016
...
check out hot projects on the Open Hub

About Project Security