NoMad: encap

NoMad currently uses epkg-0.5.1 developed by Mark Roth. Here's an HTML version of the epkg man page can be found epkg man page. It's a wonderful improvement over the old encap 1.2 and encapper utilities. To help explain how encap packages work, I've included this next secion that was borrowed from Jason Wessel's original encap 1.2 documentation.

The encap concept

The core concept to understand about encap, is that each package that you install is meant to live in its own directory. The directory that the entire package lives in should be the name of of the package. The encap program will take care of making links into the directory that the package lives in, so that users can easily access the programs.

A package directory should have the same structure as your target directory. To make the explanation easier, I will assume the place where all your package directories live is /usr/local/encap. You're target directory would be /usr/local. The goal is to be able to tell users to /usr/local/bin in their path and make all the software available to them.

Gnu software works especially well with the encap system. Therefore I will illustrate this with an example installation of less-3.2.0. The package directory is called /usr/local/encap/less-3.2.0

The encap program will make the directories and links to the files in /usr/local. /usr/local/bin/less would be a link to /usr/local/encap/less-3.2.0/bin.

Copyright © 1998 Michael K. Dopheide
Last modified: Tue Oct 13 15:48:24 CDT 1998