opencog-dev team mailing list archive
-
opencog-dev team
-
Mailing list archive
-
Message #00154
Re: preparing to move opencog to public VCS
Hi,
On Sun, 2008-05-18 at 15:22 +1000, David Hart wrote:
> I'd like to identify any issues or prerequisites for the opencog move
> from vetttalabs SVN to bzr branch lp:opencog-framework.
>
> For example, the contents of /vendor should move to
> https://edge.launchpad.net/opencog-framework/+download or other
> references/locations.
I've imported the trunk of Vettalabs' svn repository to the following
bzr repository at Launchpad:
bzr+ssh://bazaar.launchpad.net/~opencog-dev/opencog-framework/main
According to this bug: https://bugs.launchpad.net/bzr/+bug/205579,
Launchpad's version of bzr has a bug when checking out copies of a
repository that uses the 'rich-root-pack' format (which is used by bzr's
svn-import feature). So, at least for the time being, we should use one
of the workarounds described on the bug report:
$ bzr branch bzr+ssh://@bazaar.launchpad.net/~opencog-dev/opencog-framework/main <local-dir>
$ cd <local-dir>
$ bzr reconfigure --checkout
or
$ bzr init-repo --rich-root-pack <local-dir>
$ cd <local-dir>
$ bzr checkout bzr+ssh://@bazaar.launchpad.net/~opencog-dev/opencog-framework/main
The import finished at about 22:30 GMT, so if anyone has commited any
changes to the subversion repository, please reapply these changes to
the bzr repository (and start using it from now on :-) ).
On Sun, 2008-05-18 at 19:26 +1000, David Hart wrote:
> Oh, of course, all files should be copyright tagged.
The copyright headers and the license were added before the import. I've
manually added the headers/authors to all the code files but since there
were *many* files, it's likely I've missed an author here and there. If
you finds any mistakes, just let me know.
cheers,
--
Gustavo
Follow ups
References