Packaging hints for binary package distributors
===============================================

Although the source of the GNU coreutils package comes as a single package,
we recommend that for distributions that support systemd, in binary packages
the installed files be split into two packages:

   coreutils
        Contents: Programs for most purposes.
        Audience: Normal users, programmers, system administrators.
        Dependencies: no libsystemd.

   coreutils-multiuser
        Contents: Programs for multi-user functionality, namely
                  'who', 'users', 'pinky', and optionally 'uptime'.
        Audience: System administrators.
        Dependencies: requires libsystemd.

Reference: https://bugs.debian.org/1142500


Coreutils can be built as a single multi-call binary,
with links from the various utilities to this binary,
resulting in a smaller storage footprint.  E.g., on Fedora
this provides an alternative package about 1.2MB in size.

   coreutils-single
        Contents: Programs linked to a single binary
        Audience: Embedded systems, Minimal images.
        Dependencies: Optionally no GMP or OpenSSL.

Reference: https://www.pixelbeat.org/docs/conflicting-rpms.html
