Re: [OT] Scripts, packages, etc.

Nicholas E. Walker writes:
> The /package mechanism allows one to install a potentially unstable
> version of a package without needing even to set it as the system
> 'default' (i.e. the one with commands linked into /command).

There's no reason for /command entries to link directly to versions:

   /command/multilog -> /package/admin/daemontools/command/multilog
   /command/svscan -> /package/admin/daemontools/command/svscan

Links to current versions are in /package:

   /package/admin/daemontools -> /package/admin/daemontools-0.76

What matters for the current discussion is that you can have, e.g.,
/package/admin/daemontools-0.76 and /package/admin/daemontools-0.80
installed simultaneously, with the /package/admin/daemontools symlink
determining which version is used.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago