[gentoo-dev] Ebuilds and the changes people make to them

["Corey Crawford" <ccrawford@seventh.net>]

O.K.,

I'm a huge fan of ebuilds and the whole portage system.

But: who decides what changes to make in these ebuilds? I'm really getting
sick and tired of upgrading packages only to find that someone decided to
change the ./configure options the ebuild uses.

I shouldn't have to worry about my Apache server not working after an
upgrade! This is the latest example:

The '--with-suexec-docroot' configure option for the SuExec module in
Apache2's ebuild to something other than all previous Apache2 ebuilds. This
was done in apache-2.0.48-r1. _Why?_ This broke all of the CGI scripts on my
virtual hosts until it was noticed and corrected the next day.

I shouldn't have to go into every ebuild and make sure someone didn't change
paths on me before doing (what is suppose to be) a simple upgrade.

[/rant]

Has anyone considered moving any 'configure' options to another file?

Moving the 'configure' options to another file would alleviate a lot of
problems. This would allow those of us who have working systems to continue
to have functioning systems even if the default values for those configure
options have changed.

Do-able? Comments?

---
Corey Crawford
ccrawford@seventh.net


--
gentoo-dev@gentoo.org mailing list