On 10/26/05, A. S. Budden <[EMAIL PROTECTED]> wrote:
> On 25/10/05, Aaron Griffin <[EMAIL PROTECTED]> wrote:
> > On 10/20/05, James Rayner <[EMAIL PROTECTED]> wrote:
> > > On 10/19/05, Judd Vinet <[EMAIL PROTECTED]> wrote:
> > > > On Mon, Oct 17, 2005 at 06:06:17PM -0500, Aaron Griffin wrote:
> > > > > Enter the idea:
> > > > > Let's make up a file, called /etc/pacman.d/install-actions - this file
> > > > > would contain a series of file patterns to match along with commands
> > > > > to call when they are matched.
> > > >
> > > > Hi Aaron,
> > > >
> > > > Interesting, this is a similar idea to one I've been rolling around too.
> > > > Yours is more fine-grained though.  I had initially thought about some
> > > > sort of "event hooks" where you can bind actions to package name(s).
> > > > When said package(s) are upgraded, the respective actions (shell
> > > > commands, whatever) could be executed.
> > > >
> > > > Your idea works at the file level instead of the package level though.
> > > > Could be powerful.
> > > >
> > > >
> > > > - J
> > > >
> > >
> > > People would love this, like for things like a kernel update, to
> > > automatically recompile extra modules. It would be a *very* powerful
> > > feature.
> > >
> > > James Rayner
> >
> > Another case for this feature... I just upgraded mono-tools and
> > gtk-sharp, after each upgrade, it rebuilt the mono-doc index, which
> > takes ages... with this "trigger" functionality, this would have only
> > been done once.
>
> And another case for this feature... Every time I upgrade samba, I
> have to chmod 4755 `which smbmnt` in order to allow users to mount
> windows shares... not a major problem, but I almost always forget
> after doing pacman -Syu
>
> Al
>

Considering that it's a command that takes a negligable amount of
time, just throw it into /etc/rc.local, and it will do it every boot
which should cover you.

iphitus
--
iphitus - archck maintainer
Home:iphitus.loudas.com Blog: iphitus.blogspot.com

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to