Ah, you're probably right. Tagged copies are not _supposed_ to be modified, but they _can_ be. However, it might make sense to recognize the tags as tags, if the user were willing to guarantee that they really had not been modified. After all, if I've got a subversion repo with tags/release-0.1 in it, then it _looks to me_ like what I have there is release-0.1, even if it might have been altered since it was "released". But I don't know how useful that would be or how many people would be willing to make that guarantee.
Anyway, could you clarify this bit of the Tailor Manual (http://progetti.arstecnica.it/tailor/browser/README.rst#svn), where it says under the "svn" heading: "svn-tags : string Name of the directory used for tags: tailor will copy tagged revisions under this directory. /tags by default." It seems that this recognizes the /tags subdirectory in a subversion repo as something special. But when I changed /tags to /tags-renamed, it made no difference -- the /tags from subversion still came into darcs as /tags. Is this setting only for going the other way -- from darcs (e.g.) to subversion? Greg 2009 Aug 07, Lele wrote: Unfortunately there is not an easy way to figure out SVN tags, in order to apply them as darcs tags: in SVN a tag is after all just a copy of a tree somewhere else, and while it could be possible to invent a strategy/heuristic that infer the details, I think that there are lots of corner cases (just think to the fact that the copy of the tree is not immutable, or even it could be performed in several steps...) Of course I'll be happy to stand corrected! :-) On 2009-Aug-06, Gregory D. Weber wrote: > When I use tailor to import a subversion repo to darcs, using the > configuration below, > I get the full directory structure from the subversion repo (with the standard > trunk, branches, and tags subdirectories), but darcs doesn't seem to know > anything about the subversion tags: > > $ darcs show tags > $ > > If I change the [svn:source] section of the configuration file so that > module = /trunk > then I get only the trunk part of the project (with no subdirectory), > but again darcs doesn't know about the tags. > > Ideally, I would like to get just the files in trunk, but have darcs > know the subversion tags so that I could conjure up a specific release number. > Is this possible with tailor at present? If not, I think it would make > a nice feature. > > By the way, tailor is wonderfully useful even without this -- > thanks very much for developing and releasing this program! > > Configuration file follows. > > ----------------------------------------------------------------- > > [DEFAULT] > verbose = True > > [project] > target = darcs:target > start-revision = 1 > root-directory = /home/gdweber/teach/syllabi-darcs-full > state-file = tailor.state > source = svn:source > subdir = . > > [darcs:target] > module = / > repository = file:///home/gdweber/teach/syllabi-darcs-full > > [svn:source] > module = / > repository = file:///home/gdweber/svn.d/syllabi > > -- > ___ ___ __ _ > / _ \ / _ \| | | | Gregory D. Weber, Associate Professor > / /_\// / | | | /\ | | Indiana University East > / /_\\/ /__| | |/ \| | http://mypage.iu.edu/~gdweber/ > \____/\_____/\___/\__/ Tel. (765) 973-8420; FAX (765) 973-8550 -- ___ ___ __ _ / _ \ / _ \| | | | Gregory D. Weber, Associate Professor / /_\// / | | | /\ | | Indiana University East / /_\\/ /__| | |/ \| | http://mypage.iu.edu/~gdweber/ \____/\_____/\___/\__/ Tel. (765) 973-8420; FAX (765) 973-8550 _______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
