On Saturday, 18 February 2012 07:33:31 UTC, Gunnar Aastrand Grimnes wrote:
> All infrastructure will be moved, i.e. wiki-pages, issues and source code.
* I think we should leave the google code projects (i.e. do not delete
> them), but just have a front-page that links to github
* We have a good history of leaving out-dated docs around, I propose
> deleting all the google code wiki-pages NOW :)
Makes very good sense. They have been transcribed to the RDFLib GitHub wiki.
* I do not know what to do about the hg repository - there is no way
> to mark it read only - I guess I can take away everyone's commit
> rights :) OR I can delete it completely once we are sure we have
Both, I guess.
There appears to be a way to get pip to install development
> snapshots directly from hg - this relies on the hg url being in pypi -
> I could never get it to work.
Not quite sure of the context here but anyway ,,,
I've used the standard "pip install from repos" approach with success.
pip install git+https://github.com/RDFLib/rdflib.git
or, to download into ./src and setup+install from there:
pip install -e git+https://github.com/RDFLib/rdflib.git#egg=rdflib
There's also the "pip install from tarzipball" approach:
pip install https://github.com/downloads/RDFLib/rdflib/rdflib-3.2.0.tar.gz
> * @Graham: What about rdfextras - it seems the git-repos was cloned
> from hg on 25th of January, any changes I made after that are only in
> hg. I can probably roll it into one patch, and apply it to git and
> it's all good?
I went the long way round, converting the latest rdfextras-hg to git and
merging that with the github master. This approach has the advantage of
preserving the individual commits and their messages.
I've tried a few techniques for converting repos from hg to git. The one
that has proved reliable in terms of including branches and tags is
hg-fast-export and is detailed in a comment to a blog post on the subject
. It's quite terse, so I'll repeat it here for convenience (it
references Bitbucket but GitHub is a straight replacement).
Instead use hggit you may use hg-fast-export.
1. Create new git repo at Bitbucket.
2. git clone git://repo.or.cz/fast-export.git
3. mkdir new_git_repo
4. cd new_git_repo
5. git init
6. /path/to/hg-fast-export.sh -r /path/to/hg_repo
7. git checkout HEAD
8. git remote add origin g...@bitbucket.org:shaharevron/myproject.git
9. git push origin master
I've added SkipTest to a few more rdfextras tests in order to get a
(somewhat spurious) set of "blue balls" across the board for rdfextras on
the shiningpanda CI build space . I will add issue tickets as
appropriate (I was hoping to have transferred the issue lists by now but I
have been delayed).
Thanks for everyone's co-operation with this exercise and apologies for the
inconvenience - I feel that we're in a more commanding position.