Hi All, I thought I'd get the discussion of hooks for the package tools going by posting a bit of code. This is completely untested, but is encapsulates the vision I have of how hooks could be implemented. [Please excuse my rusty perl.]
The pkgutil patch implements pre/post install/remove hook capabilities that allow the admin (or other packages) to have code run at various points during the management of CSW packages. It does not differentiate between install and upgrade and it implements 'pre' and 'post' in the batch sense, not the per package sense. More granularity could be had by running hooks at each invocation of pkgadd/pkgrm, but I think that might be overkill. Thoughts? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting.
pkgutil_cswhooks.patch
Description: Binary data
signature.asc
Description: PGP signature
_______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
