From: Nathan Cutler <ncutler@suse.cz>
To: Ken Dreyer <kdreyer@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: ceph / rocksdb
Date: Thu, 25 Feb 2016 21:21:39 +0100 [thread overview]
Message-ID: <56CF6253.7020300@suse.cz> (raw)
In-Reply-To: <CALqRxCwrsTv=Lbrc98f7WLqwZxeySiAdq08E0h8a2eNyDU6SPQ@mail.gmail.com>
On 02/24/2016 06:58 PM, Ken Dreyer wrote:
> I'm really interested in getting our various bundled libraries into
> separate packages.
+1 !
> Does ceph's rocksdb have a lot of changes from rocksdb upstream? If
> so, I'm leaning towards packaging this as "ceph-rocksdb" until those
> changes are present in an upstream rocksdb release.
How about "rocksdb-ceph" for the name? To me the first component
(rocksdb) expresses what the package *is* (i.e. what you get when you
install it) and the second component (ceph) expresses the "flavor".
And does this mean I now have a green light for "civetweb-ceph"? ;-)
All the submodules should be separate packages IMO.
Also the tool "ceph-detect-init" seems like it deserves an independent
existence.
--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
next prev parent reply other threads:[~2016-02-25 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 6:05 ceph / rocksdb Marcus Watts
2016-02-24 17:58 ` Ken Dreyer
2016-02-24 18:04 ` Allen Samuels
2016-02-24 18:06 ` Sage Weil
2016-02-25 8:15 ` Marcus Watts
2016-02-25 20:21 ` Nathan Cutler [this message]
2016-06-06 10:05 ` Willem Jan Withagen
2016-06-06 10:43 ` Nathan Cutler
2016-06-06 12:26 ` Sage Weil
2016-06-06 12:29 ` Willem Jan Withagen
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=56CF6253.7020300@suse.cz \
--to=ncutler@suse.cz \
--cc=ceph-devel@vger.kernel.org \
--cc=kdreyer@redhat.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.