> I follow the "layout 1" presented in the svn book: > > package/trunk > package/tags > package/branches > > However, on my server, I have each package in its own seperate > repository. This facilitates access control on a per-project basis. > Thus, the default behavior of svn-buildpackage creates this on my server: > > package/package/trunk > package/package/tags > package/package/branches
If the repositories are stored in /home/svn, for example (as opposed
to /home/svn *being* *the* repository), you can provide file:///home/svn as
the repository URL. This assumes that the repository for "package" is stored
in /home/svn/package, though. I might still be useful if one could provide
the full repository URL and svn-inject could be made not to add the extra
directory component.
--
Magnus Holmgren [EMAIL PROTECTED]
(No Cc of list mail needed, thanks)
pgpbdNYnswdBQ.pgp
Description: PGP signature
