From: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
To: Gregory Farnum <greg@inktank.com>
Cc: dan.mick@inktank.com, ceph-devel@vger.kernel.org,
Sage Weil <sage@inktank.com>,
Watkins Noah <noah.watkins@inktank.com>
Subject: Re: [PATCH 0/6] fix build (ceph.spec)
Date: Wed, 30 Jan 2013 19:30:39 +0100 [thread overview]
Message-ID: <510966CF.6070501@bisect.de> (raw)
In-Reply-To: <92E15B6073484C53B4AE3A0B85F0FC25@inktank.com>
Am 30.01.2013 19:07, schrieb Gregory Farnum:
> On Wednesday, January 30, 2013 at 10:00 AM, Danny Al-Gaaf wrote:
>> This set fixes some issues in the spec file.
>>
>> I'm not sure what the reason for
>> #35e5d74e5c5786bc91df5dc10b5c08c77305df4e was. But I would revert
>> it and fix the underlaying issues instead.
>
>
> That is a pretty obtuse commit message, but it was actually because
> while rbd-fuse is ready to be in-tree, we don't think it's ready for
> people to be using; there are some undocumented gotchas involved with
> it and not a lot of testing. :)
Hm, but this is git master and not a released ceph version or the next
tree. IMO rbd-fuse should be installed in the master branch to be
tested. Otherwise it will be build but maybe never tested by others than
developers which know it's there.
> I'll let others comment on the Java library moves and other packaging
> changes. -Greg
Only an additional comment: I've moved the libcephfs_jni.* files to
%{_libdir} because this is what SUSE already do for e.g. the *.so files
in the libjnidispatch package.
Danny
next prev parent reply other threads:[~2013-01-30 18:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 18:00 [PATCH 0/6] fix build (ceph.spec) Danny Al-Gaaf
2013-01-30 18:00 ` [PATCH 1/6] Revert "Don't install rbd-fuse binary" Danny Al-Gaaf
2013-01-30 18:00 ` [PATCH 2/6] ceph.spec.in: add rbd-fuse Danny Al-Gaaf
2013-01-30 18:00 ` [PATCH 3/6] ceph.spec.in: move libcephfs_jni.so to ceph-devel Danny Al-Gaaf
2013-01-30 18:00 ` [PATCH 4/6] ceph.spec.in: don't move libcephfs_jni files around Danny Al-Gaaf
2013-01-30 18:00 ` [PATCH 5/6] ceph.spec.in: extend fix for libedit-devel on special SUSE versions Danny Al-Gaaf
2013-01-30 18:00 ` [PATCH 6/6] ceph.spec.in: fix file section for ceph-resource-agents Danny Al-Gaaf
2013-01-30 18:07 ` [PATCH 0/6] fix build (ceph.spec) Gregory Farnum
2013-01-30 18:30 ` Danny Al-Gaaf [this message]
2013-01-30 19:55 ` Sage Weil
2013-01-31 5:08 ` Dan Mick
2013-01-31 5:10 ` Dan Mick
2013-01-31 7:22 ` Gary Lowell
2013-02-01 7:00 ` Gary Lowell
2013-02-01 14:22 ` Danny Al-Gaaf
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=510966CF.6070501@bisect.de \
--to=danny.al-gaaf@bisect.de \
--cc=ceph-devel@vger.kernel.org \
--cc=dan.mick@inktank.com \
--cc=greg@inktank.com \
--cc=noah.watkins@inktank.com \
--cc=sage@inktank.com \
/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.