From: Paul Sokolovsky <pmiscml@gmail.com>
To: Phil Blundell <pb@reciva.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev package.bbclass: remove directories named in FILES from image after file
Date: Mon, 29 Jan 2007 00:14:24 +0200 [thread overview]
Message-ID: <153772577.20070129001424@gmail.com> (raw)
In-Reply-To: <1170022193.4354.0.camel@mebius.reciva.com>
Hello Phil,
Monday, January 29, 2007, 12:09:52 AM, you wrote:
> There shouldn't be any non-empty dirs. If you're encountering some,
> that must be a bug. Do you have a testcase?
Sure: I create a new .bb and just debug packaging. I'd prefer it
didn't throw Python exception in my face ;-). Or: I'm sure there're
few .bb which don't package all the stuff which is installed by
"make install". One such example is busybox, which creates hoards of
symlinks, but we don't packages (all of) them, instead relying on
update-alternatives.
> p.
> On Sun, 2007-01-28 at 23:30 +0200, Paul Sokolovsky wrote:
>> Hello Phil,
>>
>> What's the idea behind this change? How would if handle non-empty
>> dirs?
>>
>>
>> This is a forwarded message
>> From: pb commit <openembedded-commits@lists.openembedded.org>
>> To: openembedded-commits@lists.openembedded.org
>> Date: Sunday, January 28, 2007, 11:18:34 PM
>> Subject: [oe-commits] org.oe.dev package.bbclass: remove directories named in FILES from image after file
>>
>> ===8<==============Original message text===============
>> package.bbclass: remove directories named in FILES from image after file
>> migration
>>
[]
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-01-28 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1HBHQ2-0002RA-CZ@linuxtogo.org>
2007-01-28 21:30 ` [oe-commits] org.oe.dev package.bbclass: remove directories named in FILES from image after file Paul Sokolovsky
2007-01-28 22:09 ` Phil Blundell
2007-01-28 22:14 ` Paul Sokolovsky [this message]
2007-01-28 22:22 ` Phil Blundell
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=153772577.20070129001424@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=pb@reciva.com \
/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.