<html><head></head><body>I disagree. Since the cli will not build a volume with it, it doesn't need to be in a package. Since its value is purely academic, only the source code matters, and it will still be in the git repo and the src tarball.<br><br><div class="gmail_quote">Jay Vyas <jayunit100@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">minor point: rot-13 is a good one for learning and playing with gluster. i would suggest keeping it in the releases.!<br /><br /><br />On Jul 29, 2013, at 7:21 AM, "Kaleb S. KEITHLEY" <kkeithle@redhat.com> wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">On 07/28/2013 02:18 PM, Vijay Bellur wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">Hi All,<br /><br />There was a recent thread on fedora-devel about bloated glusterfs<br />dependency for qemu:<br /><br /><a href="https://lists.fedoraproject.org/pipermail/devel/2013-July/186484.html">https://lists.fedoraproject.org/pipermail/devel/2013-July/186484.html</a></blockquote><br />Yes, but it's all died away after it was explained properly.<br /><br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid
#ad7fa8; padding-left: 1ex;">As of today, we have the following packages and respective primary<br />constituents:<br /><br />1. glusterfs - contains all the common xlators,<br />libglusterfs, glusterfsd binary & glusterfs symlink to glusterfsd.<br />2. glusterfs-rdma - rdma shared library<br />3. glusterfs-geo-replication - geo-rep related objects<br />4. glusterfs-fuse - fuse xlator<br />5. glusterfs-server - server side xlators, config files<br />6. glusterfs-api - libgfapi shared library<br />7. glusterfs-resource-agents - OCF resource agents<br />8. glusterfs-devel - Header files for libglusterfs<br />9. glusterfs-api-devel - Header files for gfapi<br /><br />As far as qemu is concerned, qemu depends on glusterfs-api which in turn<br />is dependent on glusterfs. Much of the apparent bloat is coming from<br />glusterfs package and one proposal for reducing the dependency footprint<br />of consumers of
libgfapi could be the following:<br /><br />a) Move glusterfsd and glusterfs symlink from 'glusterfs' to<br />'glusterfs-server'</blockquote><br />We can't do that, it'll break the "client-side". You can't do a client glusterfs mount without glusterfs at least.....<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">b) Package glusterfsd binary and glusterfs symlink in 'glusterfs-fuse'</blockquote><br />Okay, but the glusterfsd binary is only about 80k — that's tiny — and the symlink is only a few bytes.<br /><br />And having the same bits in two RPMs could be a problem. I'll have to try it for myself and see, or perhaps Niels already knows, but I'd be worried that if I have both glusterfs-server and glusterfs-fuse installed and I uninstall -fuse it might remove them and break things. Not that anyone should uninstall -fuse without uninstalling -server.<br /><br /><blockquote class="gmail_quote"
style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">c) Kaleb mentioned about removing geo-replication objects from<br />'glusterfs' and having them in 'glusterfs-geo-replication' only. I think<br />that might help unless we are breaking something in geo-replication by<br />doing so. Do we remember the original intent behind packaging<br />geo-replication objects in the 'glusterfs' package?</blockquote><br />That's already in process for Fedora, and will soon be proposed for the <a href="http://glusterfs.spec.in">glusterfs.spec.in</a> as well.<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">d) Remove <a href="http://mac-compat.so">mac-compat.so</a>, <a href="http://rot-13.so">rot-13.so</a>, <a href="http://symlink-cache.so">symlink-cache.so</a> from 'glusterfs'.<br />As practically nobody uses these translators today, I don't see much<br />value in packaging
them.</blockquote><br />Good suggestion.<br /><br />-- <br /><br />Kaleb<br /><br /><hr /><br />Gluster-devel mailing list<br />Gluster-devel@nongnu.org<br /><a href="https://lists.nongnu.org/mailman/listinfo/gluster-devel">https://lists.nongnu.org/mailman/listinfo/gluster-devel</a></blockquote><br /><hr /><br />Gluster-devel mailing list<br />Gluster-devel@nongnu.org<br /><a href="https://lists.nongnu.org/mailman/listinfo/gluster-devel">https://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br /></pre></blockquote></div></body></html>