[gentoo-dev] Re: Re: Default src_install for EAPI-2 or following EAPI

[Steve Long <slong@rathaus.eclipse.co.uk>]

Thomas Sachau wrote:

> Ulrich Mueller schrieb:
>> And I still don't see why we would need the most general solution for
>> a *default* function. There's always the possibility to write your own
>> src_install() for the few ebuilds that need it.
>> 
> I aggree with Ulrich in this case.

As I said; generality in lib functions seems like a useful thing. There's a
quote I read from what is imo a classic computing text[1] (from the 70s,
never seen it referenced in any papers or anything):

"Why do we never have time to do it right,
but always plenty of time to do it over."

>                 if emake DESTDIR="${D} install || einstall ; then
missing " Don't those braces make it tricky.. ;p

> Any more comments? Good? Bad? Interested?

Given that we're okay relying on BASH, I don't think we should be scared to
use BASH effectively. Gentoo ebuild.sh should be a shining example of how
BASH is done, after eight years, not something that makes #bash folk laugh.

(I know this to be true, as when I started learning BASH, I tried dropping a
few of the lines in the channel to find out what was going on. It amazes me
that #bash is not mentioned in any of the Gentoo developer documentation,
afaict.)

In this case, you're saying "oh anyone who wants something that copes with
all filenames can do their own." IOW to do it right, we'll have to do it
over, further down the line.

BASH includes the facilities to do it right, as part of its design.

[1] "Program Style, Design, Efficiency, Debugging and Testing" van Tessel
(Prentice-Hall, 1974)