[csw-maintainers] package hooks (update)

Philip Brown phil at bolthole.com
Thu Jul 2 21:39:50 CEST 2009

On Thu, Jul 02, 2009 at 03:27:15PM -0400, Ben Walton wrote:
> Excerpts from Philip Brown's message of Thu Jul 02 15:05:30 -0400 2009:
> > Yes, it describes what [a batch hook] should do.
> > However, it does not explicitly describe how a package installation tool
> > should RECOGNIZE a batch hook, AS a batch hook, that i could see.
> The tool doesn't need to _recognize_ anything.  The hook names are
> defined.  Running a hook consists of testing for existence of a
> specific directory (based on the name of the hook) and executing in
> lexical order any files in that directory.  If the directory isn't
> there, the tool continues.  So, since hooks have names, they're
> 'addressed' by name.  No need to recognize them.

Sigh. failure to communicate here.


The general format of a hook script location, would seem to be


but you have not explicitly defined the acceptible values for DIRECTORY.

You've given a few examples. But you have not explicitly mapped out the
full space.

you have not defined which DIRECTORY names should be used for per-package,
vs "batch" hooks, for example.

More information about the maintainers mailing list