[pony-build] Next steps for Khushboo and Fatima

[Augie Fackler]

On Feb 24, 2010, at 11:33 PM, Fatima Cherkaoui wrote:

> Titus,
>
> Thanks for the ideas, I'll be working on the HgClone branch support. I
> remember that I've found some Hg-git plugin when i was trying to  
> learn more
> about mercurial,

I'm glad to answer questions.

> I don't know how it works exactly and how efficient it is
> but I will check .

TL;DR: it works via black magic.

Long version: it pulls the git packs down and converts them to revlogs  
and keeps a mapping, so it can push them back. It's slow for any  
reasonably large (eg git.git) repository. It depends on hg itself and  
dulwich, but not git.

> It might be a good idea to use it.

Not a win for you guys at all. Just use hg directly. You'll be much  
happier, and so will your users.

> Also, I'll try to write one more  build script for another package  
> along the
> way to gain more familiarity with the client side as you said.
>
>
> Fatima
>
> On Wed, Feb 24, 2010 at 11:55 AM, C. Titus Brown <ctb at msu.edu> wrote:
>
>> Hey guys,
>>
>> here are some ideas for more client-side work.
>>
>> First, you could write some more build-scripts for Python packages.
>> Any one of the mock libraries (google 'python mock') would be great,
>> for example.  Or you could ask on the 'testing-in-python' list to see
>> who would like to volunteer their package.
>>
>> One package that I know some people would like tested is 'mechanize'.
>>
>> You could also test unittest2 under several different versions of  
>> Python.
>>
>> At some point this kind of project will get really boring, but if  
>> you want
>> to continue gaining familiarity with pony-build and client-side  
>> stuff it
>> should be pretty straightforward.
>>
>> --
>>
>> Second, one of you could implement branch support for HgClone.  Right
>> now GitClone supports branches other than 'master', the default,  
>> while
>> HgClone does not support branches other than 'default'.  I know beans
>> about Mercurial, though, so this would be a reasonably independent
>> research project ;).  To get started, here are some things you  
>> could do --
>>
>> - look through the GitClone code in pony_client.py, specifically
>>  'create_repository';
>>
>> - look through the test code in client/test_client/ 
>> test_git_client.py,
>>  specifically the test_other_branch functions;
>>
>> - sign up for bitbucket and fork my pony-build-hg-test repository,  
>> and
>>  set it up with multiple branches;
>>
>> - ...fix HgClone, add a test in test_hg_client.py, etc. etc. :)
>>
>> I can hook you up with one of the Mercurial maintainers quite  
>> easily if you
>> need that level of expertise, BTW.  (You shouldn't but it's always  
>> nice to
>> have it on tap!)
>>
>> --
>>
>> And, of course, there's a whole list of ideas on the wiki, but some  
>> of them
>> are pretty big.
>>
>> --
>>
>> cheers,
>> --titus
>> --
>> C. Titus Brown, ctb at msu.edu
>>
>> _______________________________________________
>> pony-build mailing list
>> pony-build at lists.idyll.org
>> http://lists.idyll.org/listinfo/pony-build
>>
>
>
>
> -- 
>
> Fatima-Zohra Cherkaoui
>
> Activity Chair of Society of Women Engineers
> Minnesota State University,Mankato
> _______________________________________________
> pony-build mailing list
> pony-build at lists.idyll.org
> http://lists.idyll.org/listinfo/pony-build