From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Matthew McClintock <msm@freescale.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] distutils-common-base.bbclass: Pick up additional .debug folders:
Date: Fri, 24 Aug 2012 17:16:27 +0100 [thread overview]
Message-ID: <1345824987.14369.83.camel@ted> (raw)
In-Reply-To: <20120824062509.GR3029@jama.jama.net>
On Fri, 2012-08-24 at 08:25 +0200, Martin Jansa wrote:
> On Thu, Aug 23, 2012 at 11:13:08PM +0100, Burton, Ross wrote:
> > On 23 August 2012 19:46, Matthew McClintock <msm@freescale.com> wrote:
> > > ${PYTHON_SITEPACKAGES_DIR}/.debug \
> > > ${PYTHON_SITEPACKAGES_DIR}/*/.debug \
> > > ${PYTHON_SITEPACKAGES_DIR}/*/*/.debug \
> > > + ${libdir}/${PYTHON_DIR}/.debug \
> > > + ${libdir}/${PYTHON_DIR}/*/.debug \
> > > + ${libdir}/${PYTHON_DIR}/*/*/.debug \
> >
> > I thought packages that used distutils generally put their files under
> > sitepackages, and not the python base directory... Are some packages
> > doing it wrong?
>
> Yes, almost all python-* recipes after this patch
> http://git.openembedded.org/openembedded-core/commit/?id=3b23feca31480cc56f55301fd0274e622c40b522
>
> I have 9 such recipes in my dep tree.
That patch shouldn't have gone in, it breaks things. I've posted
something to try and fix things for everyone although python packaging
isn't my strong area.
Cheers,
Richard
prev parent reply other threads:[~2012-08-24 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 18:46 [PATCH] distutils-common-base.bbclass: Pick up additional .debug folders: Matthew McClintock
2012-08-23 22:13 ` Burton, Ross
2012-08-23 22:57 ` McClintock Matthew-B29882
2012-08-24 6:25 ` Martin Jansa
2012-08-24 16:06 ` McClintock Matthew-B29882
2012-08-24 16:19 ` Martin Jansa
2012-08-24 16:20 ` Richard Purdie
2012-08-24 16:16 ` 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=1345824987.14369.83.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=msm@freescale.com \
--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