1 |
On Monday 23 March 2009, Tiziano Müller wrote: |
2 |
> Spec needed. DOCS or no DOCS? |
3 |
|
4 |
DOCS, and non-empty default value, please [1]. |
5 |
Some eclasses already do this (not base, but others), and if that |
6 |
default doesn't cover it for you, the function can be overridden. |
7 |
|
8 |
Concerning the argument of declarative ebuilds vs. bash-oriented ebuilds |
9 |
brought up by Donnie: Our ebuilds always had declarative parts with an |
10 |
impact on the PM (e.g. RESTRICT), or on eclasses (WANT_AUTOCONF, or |
11 |
look at the games eclass). |
12 |
I think if we stay within sane limits[2], following this paradigm is |
13 |
going to help developers because more simple cases will be caught by |
14 |
the default implementation without adding the complexities of having to |
15 |
know tons of (aka "more than one") variables and how they interact. |
16 |
|
17 |
Robert |
18 |
|
19 |
[1] As seen here: https://bugs.gentoo.org/show_bug.cgi?id=33544#c17 |
20 |
[2] That is very fuzzy, but we're talking about introducing one variable |
21 |
in one function. Any lower limit would be to disallow. |