From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Matt Madison <matt@madison.systems>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] wic: insert local Python paths at front
Date: Mon, 7 Dec 2015 12:04:03 +0200 [thread overview]
Message-ID: <20151207100403.GA6782@linux.intel.com> (raw)
In-Reply-To: <1449420803-12282-1-git-send-email-matt@madison.systems>
Hi Matt,
Thank you for the patch!
Acked-by: Ed Bartosh <ed.bartosh@linux.intel.com>
On Sun, Dec 06, 2015 at 08:53:22AM -0800, Matt Madison wrote:
> This follows how bitbake performs path insertion, and fixes a
> failure to start wic on Ubuntu 15.10 with the distribution's
> version of python-ply installed.
>
> Signed-off-by: Matt Madison <matt@madison.systems>
> ---
> scripts/wic | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/wic b/scripts/wic
> index 7ad2b19..2286f20 100755
> --- a/scripts/wic
> +++ b/scripts/wic
> @@ -41,12 +41,12 @@ from distutils import spawn
> # External modules
> scripts_path = os.path.abspath(os.path.dirname(__file__))
> lib_path = scripts_path + '/lib'
> -sys.path.append(lib_path)
> +sys.path.insert(0, lib_path)
>
> bitbake_exe = spawn.find_executable('bitbake')
> if bitbake_exe:
> bitbake_path = os.path.join(os.path.dirname(bitbake_exe), '../lib')
> - sys.path.append(bitbake_path)
> + sys.path.insert(0, bitbake_path)
> from bb import cookerdata
> from bb.main import bitbake_main, BitBakeConfigParameters
> else:
> --
> 2.5.0
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Regards,
Ed
prev parent reply other threads:[~2015-12-07 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 16:53 [PATCH] wic: insert local Python paths at front Matt Madison
2015-12-07 10:04 ` Ed Bartosh [this message]
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=20151207100403.GA6782@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=matt@madison.systems \
--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