From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Paulo Neves <ptsneves@gmail.com>,
Yocto list discussion <yocto@yoctoproject.org>
Subject: Re: ROOTFS_RPM_DEBUG undocumented
Date: Thu, 3 May 2018 16:03:40 +0300 [thread overview]
Message-ID: <70e7860b-5b9f-45c7-5436-73859b0d3706@linux.intel.com> (raw)
In-Reply-To: <CAJO0J4gxf0ahVGCoV64Y_Z_cGtw4OiakWkSLbu2u4WB_CHzehQ@mail.gmail.com>
On 05/03/2018 01:42 PM, Paulo Neves wrote:
> # Add ROOTFS_RPM_DEBUG to the documentation;
I'd rather get rid of it, the less variables the better :)
> # Detect if we are running with debug output and enable the debugging
> output. This is the most elegant solution but I do not know how to
> detect if debug log level is turned on;
I don't think you are meant to detect that; bitbake's debug level is not
meant to affect what is being printed, but merely whether it's printed
or discarded.
> # Have dnf always print in verbose mode and print the output to
> bb.debug instead of bb.note.
I think this is the best solution actually.
> I am happy to provide a patch upon decision or suggestions.
Thank you :) Do measure the performance before and after as we don't
want to introduce a significant slowdown here.
Alex
next prev parent reply other threads:[~2018-05-03 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 10:42 ROOTFS_RPM_DEBUG undocumented Paulo Neves
2018-05-03 13:03 ` Alexander Kanavin [this message]
2018-05-03 13:37 ` Peter Kjellerstedt
2018-05-03 14:21 ` Alexander Kanavin
2018-05-04 12:42 ` Paulo Neves
2018-05-04 12:41 ` Alexander Kanavin
2018-05-04 12:43 ` Alexander Kanavin
2018-05-04 12:50 ` Scott Rifenbark
2018-05-04 12:45 ` Alexander Kanavin
2018-05-04 12:55 ` Paulo Neves
2018-05-07 9:03 ` Mirza Krak
2018-05-07 10:12 ` Alexander Kanavin
2018-05-08 9:33 ` Peter Kjellerstedt
2018-05-08 10:29 ` Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70e7860b-5b9f-45c7-5436-73859b0d3706@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=ptsneves@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.