On 23/04/16 00:07, Douglas, William wrote:
On Fri, Apr 22, 2016 at 6:32 AM, Pádraig Brady
<P(a)draigbrady.com> wrote:
> I noticed that coreutils doesn't BuildRequires: libcap-dev
> If it did, it would auto enable support for copying capabilities.
>
Oh indeed, thanks! I have updated our package with the new build dependency.
> Also I thought it worth mentioning that coreutils now supports
> being built as a single multicall binary (like busybox),
> where all functionality is available within 1M,
> which could be useful for containers etc.
> See the Fedora coreutils-single package for an example of
> how this is leveraged from RPM.
>
We would need to switch over completely to the multicall binary for us
to use it. Are there any downsides to this approach for when disk
usage doesn't need to be absolutely minimal?
Well the fedora approach was to provide the optional coreutils-single
package that one could use instead. The disadvantages are more shared
libs to resolve at startup for all utils. Now that mightn't be too bad,
especially if libselinux is not in use. Also Fedora's coreutils-single
mitigated this somewhat by not using openssl or gmp in the multicall case.
(configuring --without-openssl --without-gmp)
cheers,
Pádraig