After about 6 months of continued improvements, with several minor releases the last ~6 weeks or so to get rid of a few bugs or improve on smaller aspects of this project, a new release of the cookbooks project was finally published, in August 2015. The cookbooks project now has more features, more cookbooks, and a better tested codebase. This release features a new class called RegisteredHeaders. This class allows us to register all .h files of a given program into a yaml file. The project currently has 2794 "cookbooks" registered as of the ~end of August 2015, and it is still growing, albeit at a much slower pace than it did 10 years ago. The reason is two-fold - the more cookbooks were added, the fewer can be added, since the amount of available programs is finite. And the other reason is that I am investing less time into the project compared to 10 years ago. Still, the project is maintained consistently. You can obtain the amount of registered programs by issuing: cookbooks registered_programs? from the commandline. The Cookbooks Project is a "collection of cookbooks". What does this exactly mean? A cookbook is essentially a recipe that gives us sufficient information to compile or otherwise install a given program. Examples for this would be the PKGBUILD file in Archlinux, or the various debian controls files for distributions based on Debian. These different programs, the cookbooks, can usually be compiled from source in the event that the source is available - however had, the project also supports the plain installation of projects that do not come with the source, e. g. binary .exe files on windows, or that do not require compilation such as most ruby .gem files, as the latter are just .rb files. How does the format of a cookbook look like? Each cookbook is an individual yaml file which should contain all the required information to get it to install. Another project, class SanitizeCookbookDataset, can be used to visualize this dataset in a colourful manner. To query the information provided by this gem, you can do something such as this here: cookbooks htop This command will invoke the file stored at bin/cookbooks which is part of this project. This file will provide you, in the above example, with information about the program called "htop" (which you should have downloaded from source before, that is; you can specify alternative configurations for the source directory in the configuration file called cookbook_directory.yml). This way the Cookbooks project allows you to build the foundation for a package-manager in Ruby on top of this project. In fact, this is how the Cookbooks project originated itself - I required a separate library that could be used to query program-associated information. Another project, the RBT ("Ruby Build Tools") will then make use of that information. The latest version of July/August 2015 added the class RegisteredTags. Now you can run this file to register every available tag into a yaml file, which we can then load if we are to search for registered tags, rather than relying on "grep" itself. Thus, searching for tags will now be available as well without grep - you have to run it once to register the available programs before you can use it. I forgot to include one dependency in the last release, so the 30. July 2015 update has already fixed that. The latest release added "cookbooks last_option?" as commandline instruction, to show the last option used for configure. If you wish to support this project, for now please just test it and report any bugs or lack of documentation. It is still in beta stage and it will take a while before it can stabilize. If you have specific suggestions on how to make this gem more useful for others or for yourself, please do feel free to drop me an email at: Thank you and have fun!

Rubygem cookbooks

Total Downloads
Current Version
2015-09-08 00:00:00 UTC
First Release
2014-01-24 00:00:00 UTC


There are no comments yet, be the first to write one!

Post a comment

Markdown supported

In order to continue, you must be signed in using your Github account.

If you're signing in using this account for the first time Github will ask for your permission to give access to your public user data to the Ruby Toolbox.

Although the Github Authorization page does not mention it, the request includes read-only access to your verified email address (user:email OAuth scope). This is neccessary so there's a way to notify you about comments, information about your accepted project edits and the like. You can review your notification settings on your account page once you're signed in.