From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Python recipe
Date: Fri, 23 Mar 2012 15:02:27 +0000 [thread overview]
Message-ID: <1332514947.9740.422.camel@ted> (raw)
In-Reply-To: <4F6C8437.8020808@mlbassoc.com>
On Fri, 2012-03-23 at 08:09 -0600, Gary Thomas wrote:
> On 2012-03-23 08:06, Richard Purdie wrote:
> > On Fri, 2012-03-23 at 07:43 -0600, Gary Thomas wrote:
> >> Just curious, what is this line doing in .../recipes-devtools/python/python_2.7.2.bb
> >> DEPENDS_sharprom = "python-native db readline zlib gdbm openssl"
> >>
> >> n.b. I know what it does, I just don't know why it's there in
> >> a "core" recipe.
> >
> > Is the sharprom distro still active? I doubt it uses OE-Core? I think
> > that can be removed.
>
> Even if it is still active, this should go in a .bbappend, don't you think?
Yes.
> I have another change to this recipe - should I send them as two separate patches?
Separate please.
Cheers,
Richard
prev parent reply other threads:[~2012-03-23 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 13:43 Python recipe Gary Thomas
2012-03-23 14:06 ` Richard Purdie
2012-03-23 14:09 ` Gary Thomas
2012-03-23 15:02 ` Richard Purdie [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=1332514947.9740.422.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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