From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Which distro for OE development?
Date: Thu, 19 Nov 2009 13:37:12 +0000 [thread overview]
Message-ID: <1258637832.23826.88.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <B44D4D5BF344094DABB900C4E0F6E3533945A36F15@srv02.nortechonline.net>
On Thu, 2009-11-19 at 13:06 +0000, Hodgson, Simon wrote:
> I'm looking to make it as easy as possible to get started, so ideally all the packages I need will be available from that distro's standard repositry.
>
> I've tried SuSE in the past and given up trying to get all of the required tools installed, and more recently been using Debian, but the Python version in Debian is a few versions behind and there was talk of OE soon requiring a more up to date version.
I'm using Debian on most of my machines and I am fairly happy with it.
The python that's currently in Debian is fine for bitbake 1.8.x. By the
time OE starts to require bitbake 1.10.x, I suspect Debian's python
support will have caught up: failing that, you can always install the
package from Ubuntu.
p.
next prev parent reply other threads:[~2009-11-19 13:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 13:06 Which distro for OE development? Hodgson, Simon
2009-11-19 13:19 ` Robert P. J. Day
2009-11-19 13:54 ` Philip Balister
2009-11-19 14:02 ` Robert P. J. Day
2009-11-19 13:22 ` Marcin Juszkiewicz
2009-11-19 13:25 ` Ahsan Khawaja
2009-11-19 13:37 ` Phil Blundell [this message]
2009-11-19 13:50 ` Ricardo Salveti de Araujo
2009-11-19 13:57 ` Robert P. J. Day
2009-11-19 15:34 ` Marco Cavallini
2009-11-19 15:55 ` Bjørn Forsman
-- strict thread matches above, loose matches on Subject: below --
2008-09-02 11:42 Eliyahu Skoczylas
2008-09-02 12:35 ` Florian Boor
2008-09-02 12:43 ` Andrea Adami
2008-09-02 13:39 ` Philip Balister
2008-09-02 15:07 ` Stanislav Brabec
2008-09-02 15:19 ` Martyn Welch
2008-09-02 19:00 ` Khem Raj
2008-09-02 13:37 ` Michael 'Mickey' Lauer
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=1258637832.23826.88.camel@mill.internal.reciva.com \
--to=philb@gnu.org \
--cc=openembedded-devel@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