From: Junqian Gordon Xu <xjqian@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-issues] [Bug 2282] python_2.4.4 packaging QA issue
Date: Sat, 23 Jun 2007 02:50:50 -0500 [thread overview]
Message-ID: <467CD0DA.7020104@gmail.com> (raw)
In-Reply-To: <20070621070815.E3274402068@tinman.treke.net>
Glad to see there is a solution forming on this QA issue.
Btw, I'm taking unexpectedly trips during the last two months. Sorry for
not getting anything done in my small plate.
Gordon
> --- Comment #5 from Koen Kooi <koen@dominion.kabel.utwente.nl> 2007-06-21 00:08:15 ---
> (In reply to comment #4)
>
>> unpackaged files are now shipped -- thanks for the input.
>>
>> I agree though that it would be very handy to have a "collect everything
>> .debug" task -- since this is not related to Python, please open up another bug
>> entry where we can discuss this feature request.
>>
>
> If I may hijack this bug for a moment :)
>
> Richard and I had a talk about it, and Richard proposed to copy files when
> packaging instead of moving them, which would make it easier to remove all
> debug files from non-debug packages.
parent reply other threads:[~2007-06-23 7:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20070621070815.E3274402068@tinman.treke.net>]
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=467CD0DA.7020104@gmail.com \
--to=xjqian@gmail.com \
--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