All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/2] micro-uclibc: add xattr to distro features to fix build failure of libcap2
Date: Mon, 28 Feb 2011 18:23:24 +0000	[thread overview]
Message-ID: <1298917404.23547.37.camel@phil-desktop> (raw)
In-Reply-To: <4D697E1C.3060708@mentor.com>

On Sat, 2011-02-26 at 15:26 -0700, Tom Rini wrote:
> On 02/26/2011 12:20 PM, Phil Blundell wrote:
> > Which package in console-image depends on libcap2?  It might be worth
> > exploring whether there is a way to avoid that dependency.
> 
> avahi brings in libcap2 now.  I suppose it's possible to make that xattr 
> DISTRO_FEATURE spell that part out and update all of the distros.  But 
> maybe that can wait until post release?

Sure, waiting until post release for that sounds fine to me.  Though
judging from the recent checkins it seems as though most of the DISTROs
are declaring xattr now in any case.

Unless you have a particular objection, I'm going to revert Petr
Štetiar's original micro-uclibc.conf patch and just take the view of
"don't do that, then" for the resulting console-image failure.  If it
turns out that someone actually wants console-image on micro then I
guess we can apply some distro-specific hack to suppress the avahi
behaviour.

p.





      reply	other threads:[~2011-02-28 18:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-26 17:44 [PATCH 1/2] micro-uclibc: add xattr to distro features to fix build failure of libcap2 Petr Štetiar
2011-02-26 17:44 ` [PATCH] minimal-uclibc: " Petr Štetiar
2011-02-26 17:46   ` Petr Štetiar
2011-02-26 17:44 ` [PATCH 2/2] " Petr Štetiar
2011-02-26 18:07   ` Khem Raj
2011-02-26 18:06 ` [PATCH 1/2] micro-uclibc: " Khem Raj
2011-02-26 18:39   ` Petr Štetiar
2011-02-26 18:39 ` Phil Blundell
2011-02-26 18:59   ` Petr Štetiar
2011-02-26 19:20     ` Phil Blundell
2011-02-26 21:48       ` Petr Štetiar
2011-02-26 22:26       ` Tom Rini
2011-02-28 18:23         ` Phil Blundell [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=1298917404.23547.37.camel@phil-desktop \
    --to=philb@gnu.org \
    --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.