#73: Add documentation for branches/tags/trunk SVN assumptions
---------------------------+------------------------------------------------
Reporter: elegant_dice | Owner: lele
Type: enhancement | Status: new
Priority: minor | Milestone: VersionOne
Component: tailor | Version: 0.9
Resolution: | Keywords:
---------------------------+------------------------------------------------
Comment (by lele):
When tailor bootstraps a new project, the first thing it does is a check
to see if the URL given as ''repository'' points effectively to the root
of the repository, otherwise it won't be able to correctly understand the
paths, when parsing them from the {{{svn log}}}. There is an option,
''trust-root'', that prevents this check.
But the fact that it's ''ignoring'' some paths indicate that you used
{{{/trunk/}}} as module name in this case too: most probably, the very
first revision in the repository builds up the conventional structure of
it, so that there is a single "patch" that touches several subtrees, and
tailor ignores the entries not belonging to the tracked one. In your case,
it ignores all of them, since you are starting from a point below.
But as said, tailor has no notion about the meaning of "/branches" or
"/tags" (or "/trunk" even). It just migrate revisions touching files under
the point indicated by ''repository/module''.
Since in subversion a ''branch'' (or a ''tag'') are just simple copies of
subtrees, it has no way of determine the difference and thus recognizing
the particular meaning.
To do what you ask, the subversion project could be enriched with other
information, such as
{{{
repository = svn://some.server/svn
module = /productA/trunk/
trunk = /productA/trunk/
tags = /productA/tags/
branches = /productA/branches/
}}}
only at that point the backend would be able to recognize tags and
branches. But again it would not be simple, for example because a tag may
be retroactive (that is {{{svn cp -r 10 /productA/trunk
/productA/tags/version10}}})
--
Ticket URL: <http://progetti.arstecnica.it/tailor/ticket/73#comment:3>
Tailor <http://progetti.arstecnica.it/tailor>
An inter-VCs changeset exchanger_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
