Petteri Räty <betelge...@gentoo.org> said:
> On 03/12/2010 11:27 PM, Zac Medico wrote:
> > On 03/12/2010 11:39 AM, Petteri Räty wrote:
> >> In eclasses there's often use for outputting QA warnings for ebuild
> >> authors (at least in java and python could immediately make use of
> >> this). Currently Portage has eqawarn available but it's considered
> >> internal. Hopefully eqawarn finds it's way to the next EAPI but in the
> >> mean while do we want:
> >>
> >> 1) Do a wrapper like attached to eutils.eclass
> >> 2) Use whatever e* function that seems most appropriate (for example
> >> einfo when it's common so user LOGging setups don't get too much noise)
> >> 3) Have a speedy next EAPI if we can find more stuff like this to bundle
> > 
> > Here's another option:
> > 
> > 4) Retroactively add eqawarn to all EAPIs and use introspection to
> > call eqawarn only if available (and drop the introspection after
> > about 1 year):
> > 
> >    declare -F eqawarn >/dev/null && \
> >    eqawarn "this is ignored by older package managers"
> > 
> 
> As there was no further response and next EAPI isn't around the corner I
> propose getting the ball rolling with option 1. I will commit the patch
> next Sunday with needed documentation unless something comes up.

Could you please give a description as to when you believe this function
should be used.  Preferably as a patch for devmanual :)

Thanks,

-- 
Mark Loeser
email         -   halcy0n AT gentoo DOT org
email         -   mark AT halcy0n DOT com
web           -   http://www.halcy0n.com

Attachment: signature.asc
Description: Digital signature

Reply via email to