Bug#657401: dpkg-buildpackage: support output directory other than ..

2021-03-17 Thread Guillem Jover
On Mon, 2020-03-15 at 19:26:14 +, Nicholas Brown wrote: > I could imagine the patch below, which I started looking at some time ago > but never > got around to coming back to, could form a start at implementing this. This is pretty close to what I initially did, and mentioned on my first

Bug#657401:

2021-03-15 Thread Nicholas Brown
I could imagine the patch below, which I started looking at some time ago but never got around to coming back to, could form a start at implementing this. It was just the obvious paths within the script itself, but the various calls to dpkg-source, dpkg-genbuildinfo, dpkg-genchanges, that all

Bug#657401: experiment to build packages out-of-tree

2020-05-03 Thread Philipp Hahn
This weekend I has a look at this issue and mostly got it working, but at the end failed on two issues: 1. `dpkg-source --build $path` allows absolute paths. The `.orig.tar` files must be placed in the directory from where `dpkg-source` is invoked from. 2. Most packages nowadays use debhelper,

Bug#657401: dpkg-buildpackage: support output directory other than ..

2012-01-27 Thread Guillem Jover
On Fri, 2012-01-27 at 08:29:53 +0100, Raphael Hertzog wrote: On Fri, 27 Jan 2012, Guillem Jover wrote: Environment variables are always used to set option defaults (not commands) that always get overridden by the command line, doing otherwise would be extremely confusing, and it's just

Bug#657401: dpkg-buildpackage: support output directory other than ..

2012-01-26 Thread Guillem Jover
On Thu, 2012-01-26 at 08:29:51 +0100, Raphael Hertzog wrote: On Wed, 25 Jan 2012, Don Armstrong wrote: On Thu, 26 Jan 2012, Guillem Jover wrote: I implemented this, but then realized that it cannot be done cleanly, as dpkg-deb is called from inside debian/rules and will always place

Bug#657401: dpkg-buildpackage: support output directory other than ..

2012-01-26 Thread Raphael Hertzog
On Fri, 27 Jan 2012, Guillem Jover wrote: Of course, if there would be no constraints, I would not pick up an env variable as preferred way to pass options but there are many tools who are accepting options through the environment (think GZIP, TAR_OPTIONS, etc.). I don't see why we

Bug#657401: dpkg-buildpackage: support output directory other than ..

2012-01-25 Thread Don Armstrong
Package: dpkg-dev Severity: wishlist Version: dpkg/1.14.25 Currently, it is not trivial to have dpkg-buildpackage (or debuild) output a build package to a directory other than '..'. Support of a --output directory option with a default of '..' would avoid other tools having to parse the .changes

Bug#657401: dpkg-buildpackage: support output directory other than ..

2012-01-25 Thread Guillem Jover
On Wed, 2012-01-25 at 15:28:41 -0800, Don Armstrong wrote: Package: dpkg-dev Severity: wishlist Version: dpkg/1.14.25 Currently, it is not trivial to have dpkg-buildpackage (or debuild) output a build package to a directory other than '..'. Support of a --output directory option with a

Bug#657401: dpkg-buildpackage: support output directory other than ..

2012-01-25 Thread Don Armstrong
On Thu, 26 Jan 2012, Guillem Jover wrote: I implemented this, but then realized that it cannot be done cleanly, as dpkg-deb is called from inside debian/rules and will always place the binary packages under «..», so dpkg-buildpackage would need to move the files itself afterwards. While that

Bug#657401: dpkg-buildpackage: support output directory other than ..

2012-01-25 Thread Raphael Hertzog
Hi, On Wed, 25 Jan 2012, Don Armstrong wrote: On Thu, 26 Jan 2012, Guillem Jover wrote: I implemented this, but then realized that it cannot be done cleanly, as dpkg-deb is called from inside debian/rules and will always place the binary packages under «..», so dpkg-buildpackage would