Hi all, I'm recently having some difficulties with our current SVN layout. In fact, I like more SVN layout 2 (the one used by pkg-perl team, for example), than ours. Here's the situation. Current layout: - trunk/ -- packages/ --- <package>/ ---- branches/ ---- tags/ ---- trunk/ ----- debian/ [ with _NO_ source files ] ---- (tarballs/)* At least, this is what svn-inject created when I uploaded bioimagesuite. Here's, instead, SVN layout 2: - branches/ - tags/ - trunk/ -- (tarballs/)* -- <package>/ --- debian/ --- [ other source files ] [ * this is added manually, or by svn-buildpackage, AFAIK. ] I might agree that we save space by avoiding duplication of source code, yes, but I find it far less intuitive to, for example, create a patch for the source code: actually, in fact, I have to create the patch in some other dir where I have the source code extracted, svn commit it, svn up from the "real" directory, and svn-buildpackage from there. Probably I'm missing something, and I would be thankful for anyone who would save me from this hell. Kindly, David P.S.: bioimagesuite still doesn't build a proper Debian package; it is probably a RPATH-related issue which is confusing dpkg-shlibdeps -- it is a fact that I actually "chrpath -d"'ed all the libraries, so they get their dependencies from the usual /usr/lib/, but it still complains... :( -- . ''`. Debian maintainer | http://snipurl.com/qa_page/ : :' : Linuxer #334216 | http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://www.debianizzati.org/ `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
Attachment:
signature.asc
Description: PGP signature