Guile-PG back in the groove

Guile-PG back in the groove

[Thien-Thi Nguyen]

Greetings earthlings,

Guile-PG repo is again online, but this time, no longer at gnuvola.org.
Instead, you can find the savannah link through the new homepage:

  http://www.nongnu.org/guile-pg/

This is "non-GNU" for now until testing shows that it can work with
(the upcoming) Guile 2.x.  At that time, i will request its status be
changed to "official GNU software" and seek co-maintainers.

People can help speed up this process by trying to build/use Guile-PG
with Guile 2.x, reporting bugs, proposing patches, and so forth.  Note
that patches that break interop w/ Guile 1.4.x will not be considered.

A note about cloning: The git repo has no ‘master’ branch, even though
its HEAD points to refs/heads/master.  Presently i know of no way to
change that (as the project admin) barring asking a savannah admin to
DTRT (see my Q, end of <http://savannah.gnu.org/maintenance/UsingGit>).
Practically, this means that "git clone" will fetch successfully, but
fail on checkout.  The workaround is to:

  cd guile-pg
  git checkout -b p origin/p

manually afterwards (see file HACKING for details on ‘p’ et al).

Happy hacking,
thi

Re: Guile-PG back in the groove

[James Cloos]

>>>>> "TN" == Thien-Thi Nguyen <ttn@gnuvola.org> writes:

TN> A note about cloning: The git repo has no ‘master’ branch, even though
TN> its HEAD points to refs/heads/master.  Presently i know of no way to
TN> change that (as the project admin) barring asking a savannah admin to
TN> DTRT (see my Q, end of <http://savannah.gnu.org/maintenance/UsingGit>).

You should be able to create one in your local clone and when you push
it should just work.

If you have a file in .git/refs/heads, you can just copy that to
.git/refs/heads/master; if it is packed in .git/packed-refs you
can just copy that line and name it refs/heads/master.

That will make master identical to the branch in question.

Using the git commands, git branch should be able to do it, but I find
that copying is faster and easier. YMMV.

You might need to use the --all option to git-push to ensure that the
new master branch ref gets pushed.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

Re: Guile-PG back in the groove

[Thien-Thi Nguyen]

() James Cloos <cloos@jhcloos.com>
() Thu, 24 Jun 2010 11:57:17 -0400

   You should be able to create one in your local clone and when
   you push it should just work.

   [details]

Thanks for the tip.  The method you mention is indeed almost
equivalent to using "git branch"; the latter also updates
.git/logs/refs/heads.

The real question is whether or not it is wise to omit the
conventional branch ‘master’ in the first place.  After some
reflection (and reading your and others' comments), i've decided
that the hassle of having to explain this unconventional
arrangement as well as its workaround while savannah support
evolves towards generality outweighs the aesthetic benefit.

So, for (both Guile-WWW and) Guile-PG, i've re-added branch
‘master’, to be synchronized every so often with branch ‘p’.
These are all just node names, anyway.

Thanks to everyone who hit me w/ the clue bat.  We now return you
to your regularly scheduled "git clone" + "hack away" program.

thi