1 |
On 03/12/2010 11:39 AM, Petteri Räty wrote: |
2 |
> In eclasses there's often use for outputting QA warnings for ebuild |
3 |
> authors (at least in java and python could immediately make use of |
4 |
> this). Currently Portage has eqawarn available but it's considered |
5 |
> internal. Hopefully eqawarn finds it's way to the next EAPI but in the |
6 |
> mean while do we want: |
7 |
> |
8 |
> 1) Do a wrapper like attached to eutils.eclass |
9 |
> 2) Use whatever e* function that seems most appropriate (for example |
10 |
> einfo when it's common so user LOGging setups don't get too much noise) |
11 |
> 3) Have a speedy next EAPI if we can find more stuff like this to bundle |
12 |
|
13 |
Here's another option: |
14 |
|
15 |
4) Retroactively add eqawarn to all EAPIs and use introspection to |
16 |
call eqawarn only if available (and drop the introspection after |
17 |
about 1 year): |
18 |
|
19 |
declare -F eqawarn >/dev/null && \ |
20 |
eqawarn "this is ignored by older package managers" |
21 |
|
22 |
-- |
23 |
Thanks, |
24 |
Zac |