From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: Supporting upcoming distribution releases
Date: Tue, 12 Jul 2011 19:08:14 -0700 [thread overview]
Message-ID: <1310522900.2162.26.camel@scimitar> (raw)
In-Reply-To: <1310519752.2527.20.camel@localhost.localdomain>
On Wed, 2011-07-13 at 09:15 +0800, NiQingliang wrote:
> I think Archlinux is the preferred choice.-_-
> Just joke.
>
> I doubt why the bitbake need python2.x but just use /bin/env python. I
> think If it need a specific version python, it should write it in the
> shebang. e.g. /bin/env python2.6
I looked at this but not enough of the distributions we care to support
have a python2.6 binary:
joshual@scimitar:~
$ /usr/bin/env python2
Python 2.7.1 (r271:86832, Apr 12 2011, 16:16:18)
[GCC 4.6.0 20110331 (Red Hat 4.6.0-2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
joshual@scimitar:~
$ /usr/bin/env python2.6
/usr/bin/env: python2.6: No such file or directory
I'd love to support Arch more thoroughly but they aren't making it easy
for us ;-)
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-07-13 2:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 18:51 Supporting upcoming distribution releases Joshua Lock
2011-07-12 19:01 ` Darren Hart
2011-07-12 19:26 ` Joshua Lock
2011-07-12 20:59 ` Darren Hart
2011-07-12 21:08 ` Richard Purdie
2011-07-13 1:15 ` NiQingliang
2011-07-13 2:08 ` Joshua Lock [this message]
2011-07-13 2:19 ` NiQingliang
2011-07-13 2:31 ` Joshua Lock
2011-07-13 2:50 ` NiQingliang
2011-07-13 8:04 ` NiQingliang
2011-07-13 17:01 ` Darren Hart
2011-07-14 0:56 ` NiQingliang
2011-07-14 1:34 ` NiQingliang
2011-07-20 1:13 ` Joshua Lock
2011-07-20 2:31 ` NiQingliang
2011-07-20 2:48 ` NiQingliang
2011-07-13 6:03 ` Xu, Jiajun
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=1310522900.2162.26.camel@scimitar \
--to=josh@linux.intel.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.