From: Jeff Garzik <jeff@garzik.org>
To: Project Hail <hail-devel@vger.kernel.org>
Subject: [RFC] new structure: "hail" pkg instead of cld, chunkd
Date: Tue, 29 Jun 2010 16:56:52 -0400 [thread overview]
Message-ID: <4C2A5E14.4020809@garzik.org> (raw)
I've been thinking about a new structure for the projects, namely having
a single "hail" or "hail-core" package, that includes cld and chunkd
services, and associated client libraries inside a new libhail.
In real terms, it would look like this:
cld -> hail
libcldc -> libhail, libhail-devel
chunkd -> hail
libchunkdc -> libhail, libhail-devel
tabled -> tabled (no change)
libhttpstor -> libhail, libhail-devel
itd -> itd (no change)
nfs4d -> nfs4d (no change)
Core services (cld, chunkd), their associated client libs (libcldc,
libchunkdc), and other useful common routines (libhttpstor) would find a
new home in the hail RPM, providing cld, chunkd and libhail.
tabled, itd and nfs4d are consider hail applications, and live in their
own separate packages, BuildRequire-ing the core hail packages.
I think this new organization will be more useful to both developers and
future users. For developers, changing the core services, and packaging
commonly reused routines is easier. For users, the core services and
application separation is more clear, IMO easier to understand at a glance.
Comments?
Jeff
next reply other threads:[~2010-06-29 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 20:56 Jeff Garzik [this message]
2010-06-30 14:42 ` [RFC] new structure: "hail" pkg instead of cld, chunkd Pete Zaitcev
2010-07-01 22:58 ` Jeff Garzik
2010-07-01 23:22 ` Pete Zaitcev
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=4C2A5E14.4020809@garzik.org \
--to=jeff@garzik.org \
--cc=hail-devel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).