[Bugs] [Bug 1195947] New: Reduce the contents of dependencies from glusterfs-api

bugzilla at redhat.com bugzilla at redhat.com
Tue Feb 24 21:32:59 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1195947

            Bug ID: 1195947
           Summary: Reduce the contents of dependencies from glusterfs-api
           Product: GlusterFS
           Version: mainline
         Component: build
          Severity: medium
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: ndevos at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    hchiramm at redhat.com, kkeithle at redhat.com,
                    lmohanty at redhat.com
            Blocks: 1194503



Description of problem:
The "glusterfs" package is perceived as containing too much files. For very
slim QEMU hypervisor installations, all packages are expected to have minimal
contents.

Currently glusterfs-api pulls in the following dependencies:
- glusterfs-libs
- glusterfs

The glusterfs-libs package only contains the needed files, that is acceptable.
Unfortunately the "glusterfs" package is a 'catch' all package and contains
more files then glusterfs-api actually needs:
- xlators that can not be enabled on the client-side through the CLI
- glusterfsd binary (and glusterfs symlink)
- documentation/manpages that should not be needed for a library dependency
- logrotate config that does not apply to libgfapi logs
- /etc/sysconfig/glusterd options file
- ... maybe more?

In addition to that, the description of the sub-packages is not really correct.
The "glusterfs" package does not contain the CLI anymore, this confused some
users.

I suggest to introduce a glusterfs-client package, that contains the
client-side xlators. For libgfapi applications, the dependencies should then
become:
- glusterfs-api
- glusterfs-libs
- glusterfs-client

While this is getting done, we should check the dependencies for the
glusterfs-cli package. glusterfs-cli depends on the socket xlator (and maybe
rpc?), these would be candidates to move to glusterfs-libs. In the end,
glusterfs-cli would then become fully functional with only a dependency on
glusterfs-libs (making the vdsm people happy).


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1194503
[Bug 1194503] Dependency problem due to glusterfs-api depending on
glusterfs instead of only glusterfs-libs
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list