On Sat, 08 Jul 2006 02:00:27 +0300, Daniel Iliev wrote:

> 1) I would like to see an implementation of "PAUSE". I mean, during most
> of the emerges there is not only one package to be emerged. Some of the
> packages have instructions for additional post installation steps that
> the user
> should take. Well, I think there should be a "FETURE", a flag to
> "emerge" or
> some other mechanism to tell portage to wait for confirmation if the
> ebuild gives such information.

emerge is, by definition, a non-interactive program (apart from --ask
which works before emerge starts its business). Use the ELOG features of
portage 2.1 to have this messages save to a file, mailed to you or read
out with festival.

> 3) I hate ebuilds that are rewriting variables that I have set. For
> example I
> couldn't find a way to compile mplayer with
> "--disable-runtime-cpudetection",

EXTRA_ECONF="--disable-runtime-cpudetection" emerge --options mplayer

This doesn't work with every ebuild, but it does with most of them.

> many packages overwrite C(XX)FLAGS. They change "-O3" to "-O2" etc.
> "Gentoo is about choices" but why this happens? My opinion is that
> portage should warn about the "too aggressive setting" but to let ME
> chose to change the settings or not.

If it is know that the package will fail with -O3, what is the point of
letting it through, even if it warns you. However, an einfo message
whenever CFLAGS are overridden would be nice.
 

-- 
Neil Bothwick

I can see clearly now, the brain is gone...