On Thu, Sep 23, 2010 at 11:32 AM, Joshua Paine <[email protected]> wrote:
> On 09/23/2010 01:42 PM, Arnel Legaspi wrote:
>> Dr. Hipp, some of our developer guys wanted me to ask if there are any
>> plans in the future to create anything that would allow them to convert
>> Subversion repos over to Fossil. Are there any?
>
> I looked at doing this myself, and it's complicated by Subversion's
> everything-is-a-directory model. There aren't actually branches or
> tags--there are just copies of source trees in directories which you may
> choose to treat as a branch or tag.
>

Yes, however, if you look at how other tools deal with it, they assume
that you've set your repo up according to the standard convention.
i.e., a 'trunk' directory, a 'branches' directory, and a 'tags'
directory. And treat them as virtually separate namespaces. In general
this works pretty well - on occasion you run across repositories that
don't follow this convention, but, they usually have something similar
that you can map the idea onto,  and even multi-project repositories
can be handled well by filtering out commits not under project_foo/,
given a directory structure like so:

root/
  project_foo/
  project_foo/trunk
  project_foo/branches
  project_foo/tags
  project_bar/
  project_bar/trunk
  project_bar/branches
  project_bar/tags

I'd imagine that an import tool would at least need to handle the
following situations:
- standard_layout (trunk/, branches/, tags/)
- multi_project with standard layout per project
- non_standard layout with trunk, branches, and tags named something different
- multi_project with non_standard layout
- multi_project with shared branches and tags directories
  (one directory per project and then {tags,branches}/project_a/blah)
- only a trunk (I've seen a small repo or two that was just the code
right in the root)

I believe that would catch most common configurations.

Interestingly, while I was examining the svn dump format, I found that
svn properties actually map decently well to (raw) fossil tags, at
least in concept.

-B
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to