Re: [gentoo-portage-dev] [PATCH] pre/post phase hooks for users

[Brian Harring]

On Thu, Oct 20, 2005 at 11:37:07PM +0900, Jason Stubbs wrote:
> On Saturday 15 October 2005 07:05, Brian Harring wrote:
> > On Fri, Oct 14, 2005 at 05:02:02PM -0500, Brian Harring wrote:
> > > Jason, your thoughts on this 53 wise?
> >
> > Bleh, pardon, meant .54 for inclussion
>
> Just to be sure it's clear to everybody (although I think Brian knows
> already), my job is not to approve or disapprove of any particular change to
> any particular release. If you want to put a title on it, it'd simply be
> called "release executor". Hence, the answer to the above question really
> lies in the outcome of the .54 thread. The only small perk is that any
> suggestions I might have on the release process are quick to be
> integrated. ;)
Yah I know, but it still is fun punting stuff past you since my normal 
inclination portage wise, is for things to be a bit raw (progress 
baby). ;)

> On Tuesday 11 October 2005 17:05, Brian Harring wrote:
> > That said, their will be an exemption for java ebuilds due to the fact
> > that they're blocked by ebuild.sh env handling- they need ebd for
> > things to work properly, and in the meantime this gives them a method
> > to have things work properly.  Downside is that the pre/post hooks are
> > not available for users for java ebuilds.
>
> Why exactly would their be an exemption for java ebuilds? Are the hooks
> intended to be used with ebuild packaging as well as by users? Wouldn't new
> or altered phases serve ebuild packaging better? If it is for ebuild
> packaging, wouldn't the EAPI need to change? If it's not for ebuild
> packaging, again why the exemption?
>
> On the user side of things, will the hooks continue on into later versions?
> Specifically, with 3.0 supporting hooks on the python side will the bash
> hooks be deprecated? It seems reasonable that both can coexist nicely, so
> this is more just confirmation then anything.

Bash hooks would exist in 3.0; they're user specific hooks only, hence 
the bit about java being an evil exception till 3.0 comes to town.  I 
intend to lock down the pre/post hooks prior to ebuild sourcing under 
ebd, so ebuilds/eclasses trying to use those hooks won't be able to.

In the meantime, it's a nice abuse of a user feature that makes java 
1.4->1.5 stuff work, and works fine when 3.0 autodisables it.

Regarding EAPI, since it's user specific feature, no need; java 
ebuilds will have to depend on a portage version capable of the hooks 
however.
~harring