On 1/30/2012 6:39 PM, Ed Greshko wrote:
[re: yum-plugin-post-transaction-actions]
Well, I thought about using it...but decided to stick with my scripts.
I'm not sure if it would be the same for everyone, but it seems that
most (all) of my post yum actions result in mucking the packages such
that the benefit of the Presto plugin is negated. This, for example,
necessitates a full download of libreoffice-core. So, my scripts put
stuff back the way it needs to be to keep Presto happy.
Ed:
I haven't gotten around to trying it as I am still trying to get the
last issues resolved regarding F16 / Xfce and then have a bunch of
lingering "ToDo's" from my post to this list at the end of 2011. What I
was thinking that I'd like to get, at a minimum, is some proactive
notification when certain packages have changed. Low priority, but I
have had instances where I have to test and/or do something if something
changes.
I'm already capturing the transaction in a text file so all I would need
is a way to figure out how to tell the post-transaction which script to
use. And, as I re-read your email, I might have better control if I just
write a wrapper for yum update that writes to an output and knows to
scan that output for changes. The only way I can think to automate that
with this post-transaction would be with a pre-transaction to capture
the data to a tmp.
Another thing to that "ToDo" list,
Thanks,
Paul
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
