gregor herrmann wrote: > That's the crucial question. > > Looking in svn-inject's source code seems to indicate that "layout 2" > is already existing (despite the manpage denying it). [0] > svn-buildpackage's source looks not helpful for this question at a > short glance. > > So I tried it: > * created a new empty repo in /tmp > * svn-inject -l 2 some.dsc file:///tmp/repo -> works > * cd $package, svn-buildpackage (well, actually a wrapper, but no > other arguments than in the other case) -> works > > svn ls file:///tmp/repo looks like expected, .svn/deb-layout in the > package directory looks like expected. > > Some "real life experience" with this layout and the common tools > would be helpful but basically it seems to work. I have plenty of real life experience with the layout, though less with the svn-buildpackage tools, since I haven't used svn-inject, implemented my own svn-uupdate command (and failed to get it into the package), and use my own build script instead of svn-buildpackage. If you use svn-buildpackage --svn-tag, or svn-upgrade, they need to figure out where the tags go. They can figure this out for simple layouts, although they will fail in some edge cases (that are easily avoidable for the perl repo), and would need the .svn/deb-layout file to work around that. All the tools in devscripts (ie, debcommit) will work fine with any layout, fwiw. It's easy to write tools that do, if you just use $(svnpath tags) to get the tags directory, etc. -- see shy jo
Attachment:
signature.asc
Description: Digital signature