BUILDPKG

I Use This!

Activity Not Available

Analyzed 11 months ago. based on code collected 11 months ago.

Project Summary

Buildpkg is a package build system. It gives you the opportunity to create package system (like rpm, dpkg, stc.) independent descriptions (.def) which can be used to create binary packages on every system. It depends on a few commands / utils (see requirements), but it is a shell script. No compilcated installation required. It can be also used to track installations and create packages of the installed files. If you want more safety, you can use the 'jail' feature. In this mode a chroot-ed environment will be created from the (configurable) list of programmes and the installation will be done here. Supported package formats are : slackware's .tgz (incl. doinst script), debian's .deb (incl. postinstall), redhat's .rpm (incl. %post) and the binary only .tar.gz). Besides GNU/Linux, Solaris/SunOS (incl. postinstall) and FreeBSD (incl. postinstall) packages are also supported.

In a Nutshell, BUILDPKG...

...
has had 26 commits made by 2 contributors
representing 4,545 lines of code
...
is mostly written in shell script
with a low number of source code comments
...
has a codebase with a very short history
maintained by nobody
with stable Y-O-Y commits
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in May, 2003
ending with its most recent commit over 22 years ago

Quick Reference

Project Links:

Homepage

Code Locations:

:pserver:anonymous:@cvs.savannah...

Similar Projects:

Managers:

Become the first manager for BUILDPKG

Licenses

GNU General Public License v2.0 or later

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

This Project has No vulnerabilities Reported Against it

Did You Know...

...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
...
by exploring contributors within projects, you can view details on every commit they have made to that project
...
in 2016, 47% of companies did not have formal process in place to track OS code
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog