gregor herrmann wrote: > I'm just not very happy with svn-inject; first you have to get it > right from where to run it (probably above the ./trunk directory) and > where to import to (probably to the "root" of the test-repo); It doesn't seem to matter where you run it from. For example, I ran: joey@kodama:~>./svn-inject -l 2 -c 0 lib/debian/unstable/libtime-human-perl_1.03-1.dsc svn+ssh://svn.debian.org/svn/pkg-perl/test-repo/ This worked as I would expect, producing trunk/libtime-human-perl in the test repo. > but then it checks out the injected package to the current directory (I > guess that's your #434821). I should have re-read the man page before filing that. (-c 0) > The tarballs directory on the top level looks basically okay (if all > builders called by svn-buildpackage find it; I'm not quite sure when > it works and when it doesn't; probably an issue of .svn/deb-layout > ...); Note that tarballs are not included in svn by default. Nothing about tarballs should be changed by the changed layout AFAICS. > a build-area directory on the top level only works if > .svn/dev-layout is adjusted (or the build tool is called > appropriately). > > Maybe something like debian/svn-layout or setting the properties (cf. > `man svn-buildpackage') might be helpful. [0] > > [0] > $ cat debian/svn-deblayout > buildArea=../../build-area > origDir=../../tarballs The defaults are ../build-area and ../tarballs. That works ok if you have pkg-perl/trunk checked out and run svn-buildpackage in pkg-perl/trunk/somepackage/. Put the tarballs directory in pkg-perl/trunk/tarballs/, which is where svn-inject puts it if you run svn-inject from pkg-perl/trunk. -- see shy jo
Attachment:
signature.asc
Description: Digital signature