Re: [PATCH 0/2] Allow postinst functions to be verbose

[Peter Kjellerstedt <peter.kjellerstedt@axis.com>]

> -----Original Message-----
> From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org]
> Sent: den 14 april 2017 10:49
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 0/2] Allow postinst functions to be
> verbose
> 
> On Fri, 2017-04-14 at 04:39 +0200, Peter Kjellerstedt wrote:
> > This enables tracing of the postinst functions created in base-passwd
> > and useradd.bbclass if BB_VERBOSE_LOGS is enabled. I found this
> > extremely useful during verification of the useradd functionality,
> > especially as there otherwise is absolutely nothing in the logs of
> > why
> > a failure in a postinst function happened.
> >
> > I also simplified useradd_sysroot_sstate() by only having the code to
> > create the postinst files once.
> >
> > Feel free to squash these commits with the "base-passwd/useradd:
> > Various improvements to useradd with RSS" commit if you prefer.
> 
> I'm afraid I can't take these since these scripts get written into the
> sstate objects for the recipes in question and this would make the
> sstate change depending on the parameters you call bitbake with. I
> think we'd both agree that is undesirable.

Bother. Did not think of that (I am so used to having it enabled in all my 
builds).

> Not sure what we can do but this needs more thought.

Yeah, it would be great if the output from the postinst scripts was actually
captured. But we can think of that for 2.4.

> Cheers,
> 
> Richard

//Peter