Search Results for "packages"

COOK is a software build-automation tool made with a goal of letting you, the programmer, to utilize the most elegant and powerful programming language - Common Lisp - for managing your software builds. You write a recipe file which describes what objectives must be constructed. COOK will load and process this file, then produce either a regular Makefile or a Bourne Shell script, which will actually perform the task of building and installing your targets.

...For standard file operations MooseFS mounted with FUSE acts as other Unix-alike file systems: * A hierarchical structure (directory tree) * Stores POSIX file attributes (permissions, last access and modification times) Supports special files (block and character devices, pipes and sockets) * Symbolic links (file names pointing to target files, not necessarily on MooseFS) and hard links (different names of files which refer to the same data on MooseFS) * Access to the file system can be limited based on IP address and/or password MooseFS on GitHub: https://github.com/moosefs/moosefs Packages repository, download: https://moosefs.com/download Documentation: https://moosefs.com/support Recent changes: https://github.com/moosefs/moosefs/blob/master/NEWS

RKV allows the user to backup and restore whatever he wants in a very flexible way. The actual backup and restore procedures are supplied by the user. RKV packages and executes them, so it's a kind of framework. Written in shell.

A FreeBSD console utility that finds, lists and possibly removes unreferenced packages. It lets the user choose which packages to remove and which ones to keep. It maintains a keep-list file, so previously kept packages will be skipped automatically.

CvsKnit is a toolset to automate knitting up CVS repositories from existing source packages. This is a sub-project of minix-up project (SF.jp).

hopefully someday this can replace freebsds \"sysinstall\". At the moment it can only manage packages.