Re: [Pyobjc-dev] New Bitbucket/Mercurial copy of the SVN repository

[Lawrence A. <la...@us...>]

On Tue, 05 Jul 2011 17:02 +0200, "Ronald Oussoren"
<ron...@ma...> wrote:
>
> On 19 Jun, 2011, at 12:39, Lawrence Akka wrote:
>
> > I notice that at the end of last year Ronald said he intended to
> > move the PyObjC repository from SVN to mercurial, to join py2app and
> > friends which have already been transferred.
> >
> > In an attempt to be helpful and for my own purposes I have
> > successfully (I hope) created a copy of the PyObjC SVN repository
> > using mercurial at bitbucket: https://bitbucket.org/lakka/pyobjc
> >
> > All history/branches/tags have been preserved (though some of them
> > might usefully be closed off), but please open an issue if you find
> > any problems. I would be delighted if Ronald wanted to move/clone
> > this into his account!
> >
> > I hope soon to be able to contribute to the project some work I have
> > done reorganising the Sphinx documentation and updating the
> > examples.
>
> Cool, the documentation definitely needs work.   I also want to redo
> the website, I have to update the scripts to generate the site
> anyway because  of the move to sphinx and the site design needs some
> love as well.
>
>
> I already have a mercurial repository on my machine, but haven't
> uploaded that to bitbucket yet.
>
> BTW. I've started the port to Lion,  but that's going slower than I'd
> want. I've decided to rewrite my metadata generator using the python
> bindings to clang, the current heap of regular expressions barely
> works and causes to much problems.   From what I've seen so far it
> should be fairly easy to using clang.cindex as the parser.
>
> Ronald
>

1)  Bitbucket: By all means clone mine and become the 'master'
    repository if that is easier. I have done some optimisation to
    shrink the size of the repo, but there remains some work to do to
    close off unneeded branches etc. Alternatively, once you upload your
    version, I'll delete my own conversion.

2) Docs: Work has begun! I have reorganized/deduplicated and edited some
   of what exists at the moment, and started to write additions. At the
   moment, I am keeping this in a private patch queue, but once the
   definitive repo has been set up, I will move over to public clone.

3) Sphinx: I have also updated the docs to use the newest Sphinx, and
   had in mind seeing what I could do to generate the entire website
   using Sphinx if you would like me to.  I would only be able to turn
   to that after the bulk of the docs have been written, though.

4) Clang: interesting. I have been playing with clang compilation of
   PyObjC generally, today. Had a couple of problems with libxml though.

Lawrence