¡Hola Guido! El 2014-05-17 a las 22:18 +0200, Guido Günther escribió: > > The current behavior in import-orig is to create an orig symlink in ../ > > even if > > the user configures tarball-dir. The attached patch adds the argument > > --tarball-dir so the user can override the symlink location.
> Thanks for your patch but why would I want to create the symlink in > tarball-dir. gbp buildpackage will then create the symlink in ../ > anyways so dpkg-source etc see the correct tarball. If the tarball_dir and export_dir are set, then the gbp looks for the orig in the tarball_dir, and symlinks that into the export_dir (not in '..') If you are checking the code, keep in mind that output_dir is export_dir or '..' Later dpkg-source finds the orig inside the export_dir. This is not a perfect solution, as for multi orig packages the user needs to manualy add the symlinks in the export_dir, so dpkg-source find the orig*, but it works most of the time. Just to be clear, the specific setup I use for KDE packages is: * git repo with a master branch that only contains debian/, no pristine-tar branch, upstream branch is only local * tarball_dir is set to one directory where all the origs are downloaded * export_dir is a temporary directory, pruned after packages are uploaded -- "It takes three times the effort to find and fix bugs in system test than when done by the developer. It takes ten times the effort to find and fix bugs in the field than when done in system test. Therefore, insist on unit tests by the developer" -- Larry Bernstein Saludos /\/\ /\ >< `/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
