dpkg hooks (was Re: Upgrade report from "bo" to "hamm")
- To: email@example.com, firstname.lastname@example.org
- Subject: dpkg hooks (was Re: Upgrade report from "bo" to "hamm")
- From: email@example.com (Adam P. Harris)
- Date: 30 Jun 1998 12:31:08 -0400
- Message-id: <firstname.lastname@example.org>
- In-reply-to: Rob Browning's message of "29 Jun 1998 17:59:57 -0500"
- References: <email@example.com> <19980623104102.H19848@molec3.dfis.ull.es> <firstname.lastname@example.org> <19980623162916.A17691@abcinternet.net> <email@example.com> <firstname.lastname@example.org> <email@example.com>
Rob Browning <firstname.lastname@example.org> writes:
> Manoj Srivastava <email@example.com> writes:
> > Actually, I would like to see a hooks mechanism for the
> > package management system desgned and implemented. This can take the
> > place of the pre and post inst rm scripts; the currrent behaviour
> > just being the default hooks implemented by dpkg.
> > Thus, bbdbv could just put a reconfig request in the
> > after-package-configured-hook for VM, and that would e that.
> > The shaould also be a post-install-run-hook, and all menu call
> > and emacsen-configure calls could be added to that hook, to be
> > run when the installation is over.
> > This si a relatively simple, but very powerful technique.
> Consider this proposal seconded :>
I think I would probably agree too but I don't understand what you're
proposing. My goal was to basically de-duplicate multiple, time
consuming runs to things that lots of packages do, like update-menus.
Manoj, does your scheme address this?
.....A. P. Harris...apharris@onShore.com...<URL:http://www.onShore.com/>
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com