XEmacs source code + packages have moved to bitbucket

Michael Sperber sperber at deinprogramm.de
Fri Oct 7 07:23:40 EDT 2011


We've been getting our source-code repo services from Alioth; its
service has deteriorated to the point of making a move necessary: So,
from now on, the "master" repositories for XEmacs and its packages will
reside on Bitbucket.  We're taking this opportunity to also move the
packages from CVS on Alioth to Mercurial on Bitbucket.

Here's what you need to know:

* Pointing your existing XEmacs repo at bitbucket

In your existing repo, edit .hg/hgrc to contain this:

[paths]
default = https://bitbucket.org/xemacs/xemacs

If you have commit access, you should use:

[paths]
default = ssh://hg@bitbucket.org/xemacs/xemacs

* Checking out a fresh XEmacs repo

Do this:

hg clone https://bitbucket.org/xemacs/xemacs

or, if you have commit access:

hg clone ssh://hg@bitbucket.org/xemacs/xemacs

* Checking out the packages

Do this:

hg clone https://bitbucket.org/xemacs/xemacs-packages

or, if you have commit access:

hg clone ssh://hg@bitbucket.org/xemacs/xemacs-packages

Note: You need at least Mercurial 1.3 for this, preferably a later
version, as all the individual packages reside in subrepositories.

* Getting push access

Get an account on bitbucket.org.  Send e-mail to Mike Sperber
<mike at xemacs.org> informing him of the account name, and what exactly
you need access for.

* Notes on the packages subrepositories

The packages repository is organized as the xemacs-packages "master"
repository and one subrepository per package.  This means that each
revision of xemacs-packages contains references to specific revisions of
the subrepositories.  More info on subrepositories is available as the
output of "hg help subrepos" or here:

http://mercurial.selenic.com/wiki/Subrepository

If you're working on an individual package, just run "hg commit" *within
the directory of that package* and also run "hg push" from there.  Then
tell Norbert Koch <viteno at xemacs.org> about it (as usual), who will
make sure that the set of packages referenced from "xemacs-packages" is
consistent and push from there.

-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla



More information about the XEmacs-Beta mailing list