From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] klibc: fix packaging without moving PACKAGES and FILES_ back to recipes
Date: Wed, 2 Jun 2010 07:36:06 +0200 [thread overview]
Message-ID: <20100602053606.GH5446@jama> (raw)
In-Reply-To: <AANLkTikc5u5SS7Nxlwc0RuaXrVlYl6-JMyC9Jto0S7gm@mail.gmail.com>
On Wed, Jun 02, 2010 at 12:59:45AM +0200, Andrea Adami wrote:
> Martin,
>
> building klibc_1.5 we have the same
> NOTE: Not creating empty archive for (dmesg,sync,ls)
>
> and building 1.5.18
> NOTE: Not creating empty archive for klibc-utils-insmod-1.5.18-r14.1.5
>
> If you prefer to warn the user that it's version lacks those packages, ok.
> At first I saw them as packaging quirks in this case.
> Again, no strong opinion :)
Then it's 1:1 :), someone else with some opinion?
My point is that I see "Not creating empty archive" as harmless warning
about me using version not providing some files which some other version
does and this message I see quite often during builds..
Regards,
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
next prev parent reply other threads:[~2010-06-02 5:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1OJVCz-0003yI-GC@melo.openembedded.org>
2010-06-01 19:52 ` [oe-commits] Andrea Adami : klibc: fix packaging Martin Jansa
2010-06-01 21:47 ` [PATCH 1/2] Revert "klibc: fix packaging" Martin Jansa
2010-06-01 22:56 ` Andrea Adami
2010-06-01 21:47 ` [PATCH 2/2] klibc: fix packaging without moving PACKAGES and FILES_ back to recipes Martin Jansa
2010-06-01 22:59 ` Andrea Adami
2010-06-02 5:36 ` Martin Jansa [this message]
2010-06-02 7:54 ` Koen Kooi
2010-06-01 23:02 ` [oe-commits] Andrea Adami : klibc: fix packaging Andrea Adami
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=20100602053606.GH5446@jama \
--to=martin.jansa@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 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.