The Advent of Clib: the C Package Manager
If you’re a C programmer, you probably know this happens too much: various
.h files thrown about a repository – all of them in the single
src folder and many of them from many different authors. There can be popular dependencies such as OpenSSL and Joyent’s HTTP parser – all of them under different licenses, carrying different code standards, and rarely being correctly handled when there are updates – even critical security updates.
Despite the ubiquitous nature of C it’s sometimes difficult to find just what you need, and you’re especially lucky if it’s not part of some gigantic library of unrelated code. — TJ Holowaychuk
This issue needed to be fixed. After 40 years of being a language, C was still running into the same issues. This needed to end. Then, one day, it did.
Clib is a C package manager for the modern world - one that helps prevent programmers from reinventing a wheel that has already been invented tenfold. It already has many various packages that span from executables to benchmarking utilities, from simple string modification to even Golang
chans in C. Finally: a place where C programmers can get together and collaborate on open source, then distribute their code - in a centralized, easy way.
Clib was founded by TJ Holowaychuk (creator of Express.js). He created the original Node.js app, until Stephen Mathieson became the maintainer and ported the entire application to C. It is still primarily maintained by Stephen Mathieson, but he now has a group of contributors joining in on the project.
Publishing a package is quite easy – all you have to do is make a
package.json file with the right keys, and edit it straight to the wiki.
This is an example
package.json from my C benchmarking library:
As you can see, simplicity is key. Just commit it to GitHub and edit it into the package list; then install it with a simple
clib install <username>/<repo>.