LoneVVolf <lonewolf@xxxxxxxxx> on Thu, 2016/05/19 17:24:
> On 14-05-16 01:15, Carsten Feuls wrote:
> > Hello Everybody,
> >
> > I have some trouble with pacman hooks.
> > Arch is going to use pacman hooks in every package.
> > etckeeper was one of the first package that use pacman hooks, without any
> > trouble.
> > But now it becomes more tricky to run.
> > My Problem is that the pacman hooks run in alphabetic order.
> > And not in a Prirority order.
> >
> > How this problem could be solved?
> > Yes I know I can number every hook but I prefer a more upstream
> > solution..
> >
> >
> > Sincerly Yours
> > Carsten Feuls
> >
>
> I do think there may be better way to solve this then adding a priority
> system for hooks.
>
> this is current trigger used by etckeeper hooks :
> [Trigger]
> Operation = Install
> Operation = Upgrade
> Operation = Remove
> Type = Package
> Target = *
>
> I think the purpose of etckeeper is to keep track of changes in the /etc
> folder, right?
>
> How about using this as trigger :
>
> [Trigger]
> Operation = Install
> Operation = Upgrade
> Operation = Remove
> Type = File
> Target = /etc/*
That is what current version does. Well, except that the install root is
omitted, so correct target is just 'etc/*'.
But that does not solve the problem: Think of etckeeper hook runs
first, followed by ca-certificates hook. The changes are not committed.
That's why we want prefix for order, so etckeeper hook can run last.
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
Attachment:
pgpEp6gUWiyd0.pgp
Description: OpenPGP digital signature
