From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: provide libc-dev in glibc eglibc
Date: Fri, 22 Aug 2008 10:08:19 +0100 [thread overview]
Message-ID: <1219396099.21890.20.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <19c1b8a90808211825v497fc98jaf9aa6af3a2881d0@mail.gmail.com>
On Thu, 2008-08-21 at 18:25 -0700, Khem Raj wrote:
> This patch makes an alias for libc-dev which points to libc6-dev in
> glibc and eglibc. This makes this package have same name like uclibc.
> This helps in writing recipes which uses these dev packages to use
> just one name and do not worry about what system library is in use.
Is the existing libc-dev package (i.e. the one from uclibc) concrete or
virtual? If the former then you should call this new alias something
like "virtual-libc-dev" and make uclibc's libc-dev provide it as well.
If libc-dev is already a pure virtual then I guess adding a direct
RPROVIDES for glibc is harmless enough, though it might still be a good
idea to use the "virtual-libc-dev" naming for clarity and to avoid any
future imbroglio with other libraries.
By the way, your diffs always seem to come out with MIME-type
"application/octet-stream" which makes them a bit tedious to view.
Could you send them as something like text/diff or text/plain in future?
p.
next prev parent reply other threads:[~2008-08-22 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 1:25 provide libc-dev in glibc eglibc Khem Raj
2008-08-22 9:08 ` Phil Blundell [this message]
2008-08-22 17:27 ` Khem Raj
2008-08-22 17:47 ` 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=1219396099.21890.20.camel@mill.internal.reciva.com \
--to=pb@reciva.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.