From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/4] Add file capability/xattr support
Date: Thu, 25 Feb 2016 21:50:03 +0100 [thread overview]
Message-ID: <20160225215003.5886d69d@free-electrons.com> (raw)
In-Reply-To: <1456323992-27845-1-git-send-email-gustavo.zacarias@free-electrons.com>
Hello,
On Wed, 24 Feb 2016 11:26:28 -0300, gustavo.zacarias at free-electrons.com
wrote:
> It's done by enabling the latest fakeroot support for it, which requires
> a attr-enabled host-libcap, which in turn needs a host-attr package to
> match as well.
>
> It wasn't made optional since the time delta for a non-attr versus
> attr-enabled host-fakeroot and it's dependencies is just 5 seconds on a
> quad-core i5 - hardly worth the additional complexities.
Even if it's not that long, I'm not super happy with adding some more
packages to our default build, for a use case that is normally pretty
limited.
> TODO:
> This still needs matching makedevs support, or alternatively a separate
> option and data file to handle this functionality. It would probably be
> It's probably better to use this functionality with a separate tool and
> data file(s) to avoid clutternig the device table too much (ostensibly
> ACL support could be added as well).
So, if you think that specifying the capabilities or extended
attributes should be done via a separate data file, then it means we
will have a new option to specify this data file, and we could
therefore only bring the additional host-fakeroot dependencies only
when this option is enabled, no?
> Also not all target filesystems support extended attributes.
And possibly the above option should be made visible only when the
underlying filesystem supports extended attributes.
What do you think?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-25 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 14:26 [Buildroot] [PATCH v2 0/4] Add file capability/xattr support gustavo.zacarias at free-electrons.com
2016-02-24 14:26 ` [Buildroot] [PATCH v2 1/4] attr: add host variant gustavo.zacarias at free-electrons.com
2016-02-24 14:26 ` [Buildroot] [PATCH v2 2/4] attr: cleanup pointless indentation gustavo.zacarias at free-electrons.com
2016-02-24 14:26 ` [Buildroot] [PATCH v2 3/4] libcap: enable extended attribute support gustavo.zacarias at free-electrons.com
2016-02-24 14:26 ` [Buildroot] [PATCH v2 4/4] fakeroot: enable capability support gustavo.zacarias at free-electrons.com
2016-02-25 20:50 ` Thomas Petazzoni [this message]
2016-02-25 21:00 ` [Buildroot] [PATCH v2 0/4] Add file capability/xattr support Gustavo Zacarias
2016-02-25 21:10 ` Thomas Petazzoni
2016-02-25 21:29 ` Gustavo Zacarias
2016-02-25 21:34 ` Thomas Petazzoni
2016-02-25 21:26 ` Thomas Petazzoni
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=20160225215003.5886d69d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.