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
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
