From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Proposal to remove libattr recipe
Date: Thu, 17 Jun 2010 15:02:04 +0200 [thread overview]
Message-ID: <lyvd9hhkxf.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <20100617121913.GA16207@rhein.zuhause.netz> (Henning Heinold's message of "Thu, 17 Jun 2010 14:19:13 +0200")
Henning Heinold <heinold@inf.fu-berlin.de> writes:
> the libattr from xfsprogs clashes with the attr recipe from udev and I
> can find any recipe which uses libattr, besides libcap2 which could
> use attr from udev too. So my proposal is to remove the libattr recipe
> and switch libcap2 to use attr from udev.
Because 'xfs' is upstream for attr + acl it would be probably better to
do the opposite thing (remove these general libraries from udev/ and
update the xfsprogs/ version). Or, remove both versions and move the
best one into toplevel /attr + /acl.
Enrico
prev parent reply other threads:[~2010-06-17 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 12:19 Proposal to remove libattr recipe Henning Heinold
2010-06-17 12:32 ` Koen Kooi
2010-06-17 12:33 ` Frans Meulenbroeks
2010-06-17 13:02 ` Enrico Scholz [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=lyvd9hhkxf.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--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.