1 |
On Thu, 11 Aug 2005 08:26:49 -0400 |
2 |
Mike Frysinger <vapier@g.o> wrote: |
3 |
|
4 |
> On Thursday 11 August 2005 07:02 am, Jason Stubbs wrote: |
5 |
> > With noman and the like, how's the following for a solution? A lot |
6 |
> > of the ebuild functions contained within portage will be moving |
7 |
> > into the tree once signing is in. What about adding |
8 |
> > {pre,post}_src_{compile,install,...} hooks into portage that will |
9 |
> > live in the tree that USE="man" support can be implemented in |
10 |
> > globally? For those packages that have a specific interest, the USE |
11 |
> > flag will be available. Everything should be happy on the ebuild |
12 |
> > side of things. (On the U/I side of things, stuff can be done to |
13 |
> > cut down the noise.) |
14 |
> |
15 |
> so you're saying that the default ebuild.sh functions are going to be |
16 |
> moving into the tree to a place which will be auto-sourced before the |
17 |
> ebuild and its eclasses ? |
18 |
> -mike |
19 |
|
20 |
If you read it again you'll notice the {pre,post} part ;) |
21 |
IIRC that's already in HEAD for /etc/portage/bashrc, so extending it to |
22 |
$PORTDIR shouldn't be an issue. |
23 |
|
24 |
Marius |
25 |
|
26 |
-- |
27 |
Public Key at http://www.genone.de/info/gpg-key.pub |
28 |
|
29 |
In the beginning, there was nothing. And God said, 'Let there be |
30 |
Light.' And there was still nothing, but you could see a bit better. |