From: Benjamin Esquivel <benjamin.esquivel@linux.intel.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: "paul.eggleton@linux.intel.com" <paul.eggleton@linux.intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] populate SDK: prepare calling of bb.utils for exceptions
Date: Fri, 16 Oct 2015 15:28:06 -0500 [thread overview]
Message-ID: <1445027286.6970.34.camel@linux.intel.com> (raw)
In-Reply-To: <CABcZANkYQD8esrYrhDWZdiXnp5tEdemmh0cGyqpGWX_zA_t5fA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
On Thu, 2015-10-15 at 19:15 -0700, Christopher Larson wrote:
>
> On Thu, Oct 15, 2015 at 10:27 AM, Benjamin Esquivel <
> benjamin.esquivel@linux.intel.com> wrote:
> > + def movefile(self, sourcefile, destdir):
> > + try:
> > + # FIXME: this check of movefile's return code to None
> > should be
> > + # fixed within the function to use only exceptions to
> > signal when
> > + # something goes wrong
> > + if (bb.utils.movefile(sourcefile, destdir) == None):
> > + raise Exception("moving {} to {} failed".format(
> > + sourcefile, destdir))
> > + except Exception as e:
> > + bb.warn(str(e))
> > + bb.error("unable to place {} in final SDK
> > location".format(
> > + sourcefile))
> > +
> > + def mkdirhier(self, dirpath):
> > + try:
> > + bb.utils.mkdirhier(dirpath)
> > + except OSError as e:
> > + bb.warn(str(e))
> > + bb.error("cannot make dir for SDK:
> > {}".format(dirpath))
> >
> Shouldn't this be fatal?
correct, will change to fatal. Thanks.
[-- Attachment #2: Type: text/html, Size: 2111 bytes --]
next prev parent reply other threads:[~2015-10-16 20:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 17:27 [PATCH] populate SDK: prepare calling of bb.utils for exceptions Benjamin Esquivel
2015-10-16 2:15 ` Christopher Larson
2015-10-16 20:28 ` Benjamin Esquivel [this message]
2015-10-16 21:50 ` [PATCH V2] " Benjamin Esquivel
2015-10-19 5:27 ` Mike Looijmans
2015-10-19 15:28 ` [PATCH V3] " Benjamin Esquivel
2015-10-16 7:00 ` [PATCH] " Mike Looijmans
2015-10-16 20:27 ` Benjamin Esquivel
2015-10-16 10:01 ` Richard Purdie
2015-10-16 20:18 ` Benjamin Esquivel
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=1445027286.6970.34.camel@linux.intel.com \
--to=benjamin.esquivel@linux.intel.com \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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