hail-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Project Hail <hail-devel@vger.kernel.org>
Cc: Peter Martuccelli <peterm@redhat.com>
Subject: New 'hail' repository created, with major packaging rework
Date: Fri, 02 Jul 2010 02:59:20 -0400	[thread overview]
Message-ID: <4C2D8E48.6090902@garzik.org> (raw)


A new git repository

	git://git.kernel.org/pub/scm/daemon/distsrv/hail.git

was created, preserving the full histories of cld.git and chunkd.git. 
The existing cld.git and chunkd.git repositories have been left 
untouched, for now.  I also have not yet updated tabled.git for this new 
work, though it should be an easy matter of linking against libhail 
rather than other libs.

This new repository creates hail-$VERSION.tar.gz tarballs via "make 
distcheck", producing libhail, cld and chunkd binaries.

libhail is a single shared library binary, linking together cldc, ncld, 
libtimer, and chunkdc modules.  In other words, libhail at present is a 
simplistic combination of cld/lib and chunkd/lib.

The RPM package specfile has been updated (pkg/hail.spec) to generate 
the following complement of packages on Fedora:

Wrote: /garz/rpm/SRPMS/hail-0.7-0.1.gc69acd63.fc12.src.rpm
Wrote: /garz/rpm/RPMS/x86_64/hail-0.7-0.1.gc69acd63.fc12.x86_64.rpm
	-> contains libhail
Wrote: /garz/rpm/RPMS/x86_64/hail-cld-0.7-0.1.gc69acd63.fc12.x86_64.rpm
	-> contains cld
Wrote: /garz/rpm/RPMS/x86_64/hail-chunkd-0.7-0.1.gc69acd63.fc12.x86_64.rpm
	-> contains chunkd
Wrote: /garz/rpm/RPMS/x86_64/hail-devel-0.7-0.1.gc69acd63.fc12.x86_64.rpm
	-> contains libhail devel libs, headers
Wrote: 
/garz/rpm/RPMS/x86_64/hail-debuginfo-0.7-0.1.gc69acd63.fc12.x86_64.rpm


rpmlint still issues several warnings about hail-cld and hail-chunkd 
packages.  That must be fixed before this package suite rename can be 
submitted to Fedora (pkg renames must be submitted as new packages, and 
go through the pkg review process all over again).

To produce hail*.rpm packages on Fedora, I would do something like this:

1) set up rpm build directories (== $RBD in this example)
2) git clone git://git.kernel.org/pub/scm/daemon/distsrv/hail.git
3) cd hail
4) ./autogen.sh
5) ./autogen.sh
6) ./configure
7) make -s dist
8) cp *.tar.gz pkg/*.init pkg/*.sysconf $RBD/SOURCES
9) cp pkg/hail.spec $RBD/SPECS
10) cd $RBD
11) rpmbuild -ba SPECS/hail.spec


As mentioned above, the {cld,chunkd}.git repositories have been left 
untouched, so if something goes wildly wrong with this scheme, we can 
easily backtrack.

Comments welcome.

	Jeff




             reply	other threads:[~2010-07-02  6:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02  6:59 Jeff Garzik [this message]
2010-07-05 18:31 ` New 'hail' repository created, with major packaging rework Pete Zaitcev
2010-07-05 18:37   ` Jeff Garzik
2010-07-05 18:50     ` Pete Zaitcev
2010-07-05 19:13 ` Pete Zaitcev
2010-07-05 19:22   ` Jeff Garzik
2010-07-05 19:57     ` Pete Zaitcev
2010-07-06 12:37       ` Jeff Darcy
2010-07-06 15:24     ` Pete Zaitcev
2010-07-06 16:56       ` Jeff Garzik
2010-07-07  6:19       ` Jeff Garzik

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=4C2D8E48.6090902@garzik.org \
    --to=jeff@garzik.org \
    --cc=hail-devel@vger.kernel.org \
    --cc=peterm@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 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).