On Thu, 2013-07-18 at 18:31 +0100, Colin Watson wrote: > + * A Click package may attach to zero or more hooks, by including a "hooks" > + entry in its manifest. If present, this must be a dictionary mapping > + application names to hook sets; each hook set is itself a dictionary > + mapping hook names to paths. The hook names are used to look up > + ``*.hook`` files with matching base names. The paths are relative to the > + directory where the Click package is unpacked, and are used as symlink > + targets by the package manager when creating symlinks according to the > + ``Pattern`` field in ``*.hook`` files.
Sorry to be late and responding, vacation got in the way of e-mail. I object to the concept that a package may attach to hooks. I think that it involves the implementation into the manifest file. We want the manifest file to provide information, the hooks to use that information, but we don't want applications to determine which hooks need to be installed on the system. For instance, if the Kubuntu guys wanted to provide a hook that would do something special for KDE Active, that should be allowed and individual applications shouldn't be able to disable or enable that. I think it would be better to instead have all the hooks get executed, and they decide themselves whether they do something with the given manifest. This way we can add and remove hooks without having to adjust any deployed applications. Ted
signature.asc
Description: This is a digitally signed message part
-- Mailing list: https://launchpad.net/~ubuntu-appstore-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-appstore-developers More help : https://help.launchpad.net/ListHelp
