| 1 |
On Monday 25 September 2006 01:34, Jerry McBride wrote: |
| 2 |
> On Sunday 24 September 2006 19:16, Bo Ørsted Andresen wrote: |
| 3 |
> > On Sunday 24 September 2006 23:05, Jerry McBride wrote: |
| 4 |
> > > Well... it's time I revisited my /etc/portage/bashrc file, now that |
| 5 |
> > > Portage 2.1 is vogue. My old bashrc doesn't work anymore and things |
| 6 |
> > > have changed sufficiently with 2.1 that I need some help... |
| 7 |
> > > documentation. |
| 8 |
> > > |
| 9 |
> > > Would anyone happen to know where the API for Portage 2.1, that |
| 10 |
> > > explains the new hook framework layout? |
| 11 |
> > |
| 12 |
> > I'm not sure such documentation exists... What do you want to do? |
| 13 |
> |
| 14 |
> I had a bash script that would simply delete the archives downloaded to |
| 15 |
> distfiles, after the emerge completed. Really a handy thing to have, |
| 16 |
> managed my distfiles automaticly. It doesn't work anymore since the upgrade |
| 17 |
> to portage 2.1.x. |
| 18 |
> |
| 19 |
> I could fix it, but the hooks have either moved or have been eliminated in |
| 20 |
> favor of some other mechanism. Hence my need for documentation or tips... |
| 21 |
|
| 22 |
I'm not really sure I get this right. Did you want to keep your distdir empty |
| 23 |
after each merge or did you want to get rid of sources when they are no |
| 24 |
longer needed? If the latter why don't you use eclean from |
| 25 |
app-portage/gentoolkit? If you wanted something completely different then |
| 26 |
please elaborate... |
| 27 |
|
| 28 |
-- |
| 29 |
Bo Andresen |
Archives