From: "João Henrique Ferreira de Freitas" <joaohf@gmail.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] cml1.bbclass: Add fragmentconfig task to cml1
Date: Sat, 15 Feb 2014 21:51:28 -0200 [thread overview]
Message-ID: <20140215215128.5be9fa1d@joaohf-desktop> (raw)
In-Reply-To: <CF2152C5.6CB8D%dvhart@linux.intel.com>
Hi Darren,
> $ bitbake linux-yocto -c diffconfig
>
> I like the latter because it is consistent in naming, <action>config,
> with menuconfig.
>
Ok.
> >+ try:
> >+ md5newconfig = bb.utils.md5_file(configorig)
> >+ md5config = bb.utils.md5_file(config)
> >+ isdiff = md5newconfig != md5config
> >+ except OSError:
>
> We should be doing something to indicate failure here.
Ok.
>
> >+
> >+ statement = 'diff -Nurp ' + configorig + ' ' + config + '|
> >sed -n "s/^\+//p" >' + fragment
> >+ subprocess.call(statement, shell=True)
> >+
> >+ shutil.copy(configorig, config)
>
> We should be printing something to make it easy for the user to find
> the fragment.
I've suppose that the bb.note did it. But the messages doesn't appear
on console. Only in the log.do_diffconfig log file.
What is the trick here? Should I use bb.warn() or logger.info() ?
Thanks.
--
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
next prev parent reply other threads:[~2014-02-15 23:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 0:20 [PATCH 0/2] Add task to create kernel config fragments João Henrique Ferreira de Freitas
2014-02-13 0:20 ` [PATCH 1/2] kernel-yocto: Add do_fragmentconfig task João Henrique Ferreira de Freitas
2014-02-13 0:20 ` [PATCH 2/2] cml1.bbclass: Add fragmentconfig task to cml1 João Henrique Ferreira de Freitas
2014-02-13 0:45 ` Darren Hart
2014-02-15 23:51 ` João Henrique Ferreira de Freitas [this message]
2014-02-13 11:33 ` Richard Purdie
2014-02-13 19:00 ` Darren Hart
2014-02-14 15:46 ` Richard Purdie
2014-02-14 16:15 ` Darren Hart
2014-02-14 16:44 ` Richard Purdie
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=20140215215128.5be9fa1d@joaohf-desktop \
--to=joaohf@gmail.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox