[gentoo-dev] Re: Feedback on new ebuilds

[Paul]

Evan Read <eread@×××××××××.org>, on Mon Oct 07, 2002 [08:06:52 AM] said:
> On Sun, 2002-10-06 at 15:57, Mike Frysinger wrote:
> > > Bogofilter is ok except upstream (the venerable ESR) hasn't used a
> > > configure script so the make process doesn't use custom CFLAGS unless
> > > they are overridden. I can manually override them, but can anyone
> > > suggest how I can get the settings from make.conf into the ebuild?
> > one common way is to do a `sed` on it ...
> > cp Makefile Makefile.orig
> > sed -e "s:TEXT TO FIND:TEXT TO REPLACE WITH:" Makefile.orig > Makefile
> > make
>
> I would need to grep the make.conf for the appropriate line, wouldn't I?
> I haven't figured that CFLAGS is an environment variable anyware.
>
> I can match the right line with grep, but I haven't figured out how to
> store the match in another var I could then use thus:
>
> # cat /etc/make.conf | grep ^CFLAGS=
> result of grep or something stored in $1 	<- Perl Like ;)
> # make $1     					<- which will override the CFLAGS in the makefile
>
> Suggestions?  I thought this to be the easiest way. I could redirect
> grep to a file, but would rather keep it in memory.
>
	
	Hi;

	If you have a problem with making an ebuild, most times,
it has been encountered and solved in an existing ebuild. One
way to find them is with rgrep, or something like:

find /usr/portage -name "*.ebuild" -exec grep -i REGEXP {} /dev/null \;

	Where, in your case 'CFLAGS' might be a good REGEXP
string.  I believe make.conf is basicly a collection of env
variables, which are available to an ebuild. eg. ${CFLAGS} and
${CXXFLAGS} are set for you.
	Other peoples ebuilds often make interesting reading.
Good luck!

Paul
set@×××××.com