Quoting Robert Dodier <robert.dodier at gmail.com>:
> On 2/13/11, Leo T Butler <l.butler at ed.ac.uk> wrote:
>
>> -setup_help_database &
>> -print_help_database
>
> print_help_database suggests it's going to display the
> help db on the console. Maybe store_help_database is
> more accurate.
The default behaviour is to print to the console; it
will print to a file is a filename is given it. Also,
there is a third hashtable that is saved, which contains
the info filenames. So I think the name is accurate.
>
> Does the constructed index work OK with multibyte character
> encodings? I seem to recall some byte versus character subtleties.
I believe that I have sidestepped all the perl-ish problems by
using Lisp, and I have written a short testsuite (see
tests/rtest-build-index.lisp), that includes tests with the english,
german and spanish
info files.
But, this is why I am interested in users of trying this out.
>
>> 3. I have mirrored Maxima's sourceforge CVS repository on GitHUB. You
>> can pick up the above code by (install git, then...)
>
> Hmm, I don't have anything against you maintaining whatever
> you want but I wonder if we as a group want to put the source
> code on Github or on Sourceforge. (SF has Git I'm pretty sure.)
I think that we want to migrate the CVS repository to a Git repository
on Sourceforge, but definitely we want to keep the *definitive*
repository on Sourceforge.
I put the *mirror* on Github for 3 reasons: 1/ the re-write of
build-index was more sweeping than I originally expected and I would
like to have feedback before committing it to the `official'
repository; 2/ I am a git newbie and I was curious to see how
difficult it would be to migrate; 3/ the recent SF outage affected CVS
services the most, but it affected all services, so a public mirror
seems like a reasonable idea, and git gives us the flexibility to
switch between repos quite painlessly (or even pushing to both at the
same time).
>
> It appears you were able to import branches from CVS
> but not tags. Or maybe you didn't try to import tags?
> Were there any gotchas in the Git import?
I just imported the branches, that's correct.
It was absolutely painless: I imported the CVS repo,
added my branch, then I setup the github repo and pushed
all the branches to github. I think there were a couple that
git balked at, because they were out of historical order and there
were implied deletions of files, but if I re-ran the push with the
--force flag, git will push those branches, too.
I didn't try to import tags to the github repo, but I can see that git
did import tags from the CVS repo to my git repo. Apparently there are
issues with cvs->git and tags, so I won't swear that the job is done
correctly.
The git-tag manpage suggests trying cvs2git (in cvs2svn) if tags are
an issue.
----
Out of the box, git was much nicer to use than mercurial (I use the latter
on a googlecode project, and I find it really pretty bearish at times).
Leo
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.