Hooks for Portage 2.1?

Well... it's time I revisited my /etc/portage/bashrc file,
now that Portage 
2.1 is vogue. My old bashrc doesn't work anymore and things
have changed 
sufficiently with 2.1 that I need some help...
documentation.

Would anyone happen to know where the API for Portage 2.1,
that explains the 
new hook framework layout?

Thanks.

Jerry

-- 
gentoo-usergentoo.org mailing list

On Sunday 24 September 2006 23:05, Jerry McBride wrote:
> Well... it's time I revisited my /etc/portage/bashrc
file, now that Portage
> 2.1 is vogue. My old bashrc doesn't work anymore and
things have changed
> sufficiently with 2.1 that I need some help...
documentation.
>
> Would anyone happen to know where the API for Portage
2.1, that explains
> the new hook framework layout?

I'm not sure such documentation exists... What do you want
to do?

-- 
Bo Andresen

On Sunday 24 September 2006 19:16, Bo Ørsted Andresen wrote:
> On Sunday 24 September 2006 23:05, Jerry McBride wrote:
> > Well... it's time I revisited my
/etc/portage/bashrc file, now that
> > Portage 2.1 is vogue. My old bashrc doesn't work
anymore and things have
> > changed sufficiently with 2.1 that I need some
help... documentation.
> >
> > Would anyone happen to know where the API for
Portage 2.1, that explains
> > the new hook framework layout?
>
> I'm not sure such documentation exists... What do you
want to do?

I had a bash script that would simply delete the archives
downloaded to 
distfiles,  after the emerge completed. Really a  handy
thing to have, 
managed my distfiles automaticly. It doesn't work anymore
since the upgrade 
to portage 2.1.x. 

I could fix it, but the hooks have either moved or have been
eliminated in 
favor of some other mechanism. Hence my need for
documentation or tips...

Jerry

-- 
gentoo-usergentoo.org mailing list

On Monday 25 September 2006 01:34, Jerry McBride wrote:
> On Sunday 24 September 2006 19:16, Bo Ørsted Andresen
wrote:
> > On Sunday 24 September 2006 23:05, Jerry McBride
wrote:
> > > Well... it's time I revisited my
/etc/portage/bashrc file, now that
> > > Portage 2.1 is vogue. My old bashrc doesn't
work anymore and things
> > > have changed sufficiently with 2.1 that I
need some help...
> > > documentation.
> > >
> > > Would anyone happen to know where the API for
Portage 2.1, that
> > > explains the new hook framework layout?
> >
> > I'm not sure such documentation exists... What do
you want to do?
>
> I had a bash script that would simply delete the
archives downloaded to
> distfiles,  after the emerge completed. Really a  handy
thing to have,
> managed my distfiles automaticly. It doesn't work
anymore since the upgrade
> to portage 2.1.x.
>
> I could fix it, but the hooks have either moved or have
been eliminated in
> favor of some other mechanism. Hence my need for
documentation or tips...

I'm not really sure I get this right. Did you want to keep
your distdir empty 
after each merge or did you want to get rid of sources when
they are no 
longer needed? If the latter why don't you use eclean from 
app-portage/gentoolkit? If you wanted something completely
different then 
please elaborate...

-- 
Bo Andresen

On Mon, 25 Sep 2006 01:48:14 +0200, Bo Ørsted Andresen
wrote:

> If you wanted something completely different then 
> please elaborate...

Or post the script so we can try to see where it goes wrong.


-- 
Neil Bothwick

Old hitchhikers never die-they just throw in the towel.

hi,

> > Would anyone happen to know where the API for
Portage 2.1, that explains
> > the new hook framework layout?
> 
> I'm not sure such documentation exists... What do you
want to do?

i would like to have a script (usage e.g. "emerge_patch
package path/patch_file")
which would emerge a given package and apply given patch
after source unpack phase.
as i understood some time ago the hooks could be used for
it, but i havent found
any hint how to use them.

pavel
-- 
gentoo-usergentoo.org mailing list

On Friday 29 September 2006 23:03, pstwin.jikos.cz wrote:
> i would like to have a script (usage e.g.
"emerge_patch package
> path/patch_file") which would emerge a given
package and apply given patch
> after source unpack phase. as i understood some time
ago the hooks could be
> used for it, but i havent found any hint how to use
them.

I don't think the hooks are useful for that. Why not just
copy the ebuild to 
an overlay and apply the patch in the ebuild in the overlay?
I think [1] 
tells you everything you need to know to do that?

[1] http://gentoo-wiki.com/HOWTO_Create_an_Updated_Ebuild

-- 
Bo Andresen

> I don't think the hooks are useful for that. 

i have been told to use these two:
post_src_unpack/pre_src_compile
(but dont know how).

> Why not just copy the ebuild to 
> an overlay and apply the patch in the ebuild in the
overlay?

basically because its tedious to make new ebuild for each
new version for
a given package when i have some particular patch i always
want to apply.

pavel
-- 
gentoo-usergentoo.org mailing list

On Saturday 30 September 2006 19:32, pstwin.jikos.cz wrote:
> > I don't think the hooks are useful for that.
>
> i have been told to use these two:
> post_src_unpack/pre_src_compile
> (but dont know how).
>
> > Why not just copy the ebuild to
> > an overlay and apply the patch in the ebuild in
the overlay?
>
> basically because its tedious to make new ebuild for
each new version for
> a given package when i have some particular patch i
always want to apply.

Hmm... Well, if you want to apply foo.patch on category/name
all you really 
need to do should be something like:

# mkdir -p /etc/portage/env/category && echo
"post_src_unpack() {
        epatch /absolute/path/to/foo.patch
}" >> /etc/portage/env/category/name

-- 
Bo Andresen

> Hmm... Well, if you want to apply foo.patch on
category/name all you really 
> need to do should be something like:
> 
> # mkdir -p /etc/portage/env/category && echo
"post_src_unpack() {
>         epatch /absolute/path/to/foo.patch
> }" >> /etc/portage/env/category/name
> 

thanks a lot )
even that emerge_patch script could be done using this.

pavel
-- 
gentoo-usergentoo.org mailing list