Portage Hooks

15 views

Skip to first unread message

Jacob Godserv

unread,

Jan 21, 2012, 11:40:18 AM1/21/12

to neuvoo

Just so you guys know. last year I told the portage developers to hold
off until I had a chance to review it again, because I felt uneasy
about how our hooks had to actually kill portage to work. I've since
fixed the feature, and resubmitted it for their attention:
https://bugs.gentoo.org/show_bug.cgi?id=272988#c25

Now pre-run and pre-sync hook scripts can exit with code 3 to indicate
that they succeeded, but need portage to consider its job done and
quit successfully before it does anything else. This is excellent for
our squashfs-portage hook, which has a pre-sync hook that completely
takes care of syncing. Allowing portage to do its own sync would cause
portage to crash and burn, so now the squashfs-portage hook can tell
portage that its sync job was handled and it can just quit.

--
Jacob

"For then there will be great distress, unequaled
from the beginning of the world until now — and never
to be equaled again. If those days had not been cut
short, no one would survive, but for the sake of the
elect those days will be shortened."