Gentoo Archives: gentoo-dev

From: Mike Frysinger <vapier@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] We have "doc" USE flag, why not a "man" USE flag too
Date: Thu, 11 Aug 2005 14:05:10
Message-Id: 200508111003.13901.vapier@gentoo.org
In Reply to: Re: [gentoo-dev] We have "doc" USE flag, why not a "man" USE flag too by Marius Mauch
1 On Thursday 11 August 2005 09:40 am, Marius Mauch wrote:
2 > On Thu, 11 Aug 2005 08:26:49 -0400
3 >
4 > Mike Frysinger <vapier@g.o> wrote:
5 > > On Thursday 11 August 2005 07:02 am, Jason Stubbs wrote:
6 > > > With noman and the like, how's the following for a solution? A lot
7 > > > of the ebuild functions contained within portage will be moving
8 > > > into the tree once signing is in. What about adding
9 > > > {pre,post}_src_{compile,install,...} hooks into portage that will
10 > > > live in the tree that USE="man" support can be implemented in
11 > > > globally? For those packages that have a specific interest, the USE
12 > > > flag will be available. Everything should be happy on the ebuild
13 > > > side of things. (On the U/I side of things, stuff can be done to
14 > > > cut down the noise.)
15 > >
16 > > so you're saying that the default ebuild.sh functions are going to be
17 > > moving into the tree to a place which will be auto-sourced before the
18 > > ebuild and its eclasses ?
19 > > -mike
20 >
21 > If you read it again you'll notice the {pre,post} part ;)
22 > IIRC that's already in HEAD for /etc/portage/bashrc, so extending it to
23 > $PORTDIR shouldn't be an issue.
24
25 and if *you* read it again you'll notice that he said moving a lot of ebuild
26 functions out of ebuild.sh *and* adding new {pre,post} hooks
27
28 personally i dont think bashrc is appropriate for this ...
29 -mike
30 --
31 gentoo-dev@g.o mailing list

Replies