[gentoo-portage-dev] Re: Portage phase hooks patch

[Mike Kelly]

On Mon, 24 Jul 2006 21:22:20 +0200
Marius Mauch <genone@g.o> wrote:

> > The problem with having these in the tree is that they should be
> > able to take advantage of the unique features of each package
> > manager. Otherwise, they really are just eclasses.
>
> "unique features" such as? What exact benefits does this hooks system
> give you over using an eclass?

The biggest one is the ability to clean up after myself if the emerge
fails (if the fail hooks idea I mentioned in my previous mail makes
sense, at least).

Basically, what I need to do is:

 - Run a script to intelligently add / manage package manager-added
   users. At the moment, it would seem this should just be run before
   or during the pkg_setup phase, but this may well be sub-optimal,
   particularly in the case if binary packages or non-standard ROOTs.

 - Properly let that set of scripts know when an added user or group is
   safe to remove. This code is intimately tied with the
   implementation-specific details of the above scripts, which may
   change from version to version, hence my trepidation about adding
   this code directly into portage itself.

 - Have the ability to clean up from myself if a build goes awry, or
   is aborted by the operator. As far as I know, this particular
   requirement would exclude the use of eclasses, but I could well be
   wrong.

 - Have this user addition handled in an intelligent way when we're
   only building/installing a binary package. I'm not really sure on
   what would be a logical way to do this.

So, if the answer to the above is to not use some sort of hooks, then I
would appreciate pointers on where to look to achieve all of the above
with portage.

Thanks for all your patience with me.

-- 
Mike Kelly