From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Tree split completed (READ CAREFULLY!)
Date: Wed, 7 Jan 2009 15:47:55 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0901071528010.15762@trider-g7> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi everybody,
as of now, cluster.git master branch has been split into several projects.
NOTE TO PACKAGERS/USERS: do _NOT_ package/use those trees. This is the
beginning of a new development stage, they will be extremely unstable and
not suitable for production. We will not accept bug reports or provide any
support on those trees for a long time.
The main consequence for all developers is that fixes and changes need to
be propagated in more trees and branches.
The new projects only have "master". For all the other branches,
cluster.git is and will remain the authoritative tree.
If you are unsure where a commit should go, please ask.
The new projects/trees are:
http://git.fedorahosted.org/git/cluster.git
http://git.fedorahosted.org/git/dlm.git
http://git.fedorahosted.org/git/fence.git
http://git.fedorahosted.org/git/fence-agents.git
http://git.fedorahosted.org/git/gfs1-utils.git
http://git.fedorahosted.org/git/gfs2-utils.git
http://git.fedorahosted.org/git/rgmanager.git
http://git.fedorahosted.org/git/resource-agents.git
Everybody with commit access (FAS) to cluster.git has automatically
access to all the trees.
In order to build the new trees:
- - make sure to deinstall everything from the previous versions of the
stack.
- - checkout all of the above
- - configure, build, install each tree in the following sequence:
* cluster.git
* fence.git
* dlm.git
* rgmanager.git
* gfs2-utils.git
* gfs1-utils.git
* fence-agents.git
* resource-agents.git
(PS I am perfectly aware that the order can be slightly modified here and
there.. this is just one way)
In order to avoid complex build issues, the new trees will install 3
static libraries (and 3 headers) more on your system. Those libraries will
either disappear in time (libgroup for example) or turned into proper
shared libraries later on.
The only known regression compared to the old monolithic tree is the lack
of group_tool. At this point in time it's the only tool that requires a
complex bootstrapping but it will be addressed... just not today.
There is still a lot of cleaning that needs to be done on those tree in
respect of configure/Makefile and doc bits. Please be patience and report
to me any build related issue.
If you have any questions please don't esitate to ask.
Happy hacking!
Fabio
- --
I'm going to make him an offer he can't refuse.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iQIVAwUBSWTAoQgUGcMLQ3qJAQIDAQ/9HqEZeFb7SFYqPz4sFcQsTaLKB2x95IrT
yv0drgoyKYMMwdmQG8t36O8CnQM+spV77UjnGXkMz118AVPaXJGa9OvodvOSiwep
ch2iwUnUmP2CuuZFE3IfpKjJY6SH1w4CyEQX0zgt/8Jwk3LQqgZ7LvzWTc1pWFTT
JR8F+p4Rjibwc6iidnNMgclcIsO6FmtOpXPs5fexBoCr0w7nJDDKk2N695N9rsg7
u20H7V7yabC3xOuTtIrHnRNtWCz7F78nqMEEYTjg3th2R5+Ydv+nwO8Cfq+39b2Q
OsqYhbxYR6l+LMGbMtUGfL9MDzwkPHzUXEPtp3/ligvfMH5C4WSKOWy3UQV7y2vY
S75h7EieBBSyabqz3qcl+M2wOQUIcprBWLQKgF2d/DmdBDcBGbrX1EYqlmUFY0kZ
NS/FHipQ1W6ep3tGBkipmaR2W3icVYN071v6Cqiueb6rBRlBN2sUOxbghDI1b8j+
wi+qMlkFVRbby+LR8Ruh/3Kbh6cqhUzu4GhVK/6dDJo4f8zICePHA0FfrkD4ZGBr
UL1mjkVflhgswBueVyOLOnHVoQHVKJKnHzMwcxRfj14cRfmMryNelKBUvDf0ScUT
2eXr6fgkIMixLFIM5JIAHVmvFnjT9q00oacHuINjiz3du+SGRflSxV9Yl60Lkx7T
WVx1rRbaQ2U=
=cNqy
-----END PGP SIGNATURE-----
next reply other threads:[~2009-01-07 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 14:47 Fabio M. Di Nitto [this message]
2009-01-09 19:42 ` [Cluster-devel] Tree split completed (READ CAREFULLY!) Lon Hohberger
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=Pine.LNX.4.64.0901071528010.15762@trider-g7 \
--to=fdinitto@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 NNTP newsgroup(s).