On Tue, Dec 14, 2004 at 01:42:40PM -0800, [EMAIL PROTECTED] wrote:
> Why is debhelper using debian/tmp/ as build directory, instead of
> debian//?
As people has said, it is the compatibility version.
> It is a kernel module source package; I build it using make-kpkg. I
> used dh_make to create
hi,
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2004-12-15 18:00]:
> Why is debhelper using debian/tmp/ as build directory, instead of
> debian//?
>
> The debhelper documentation agrees with my experience, that it uses
> debian// by default, but one of my packages is using
> debian/tmp/, withou
Read debhelper(7); in short, `echo 4 >debian/compat` makes it do what
you want.
Justin
On Tue, Dec 14, 2004 at 01:42:40PM -0800, [EMAIL PROTECTED] wrote:
> Why is debhelper using debian/tmp/ as build directory, instead of
> debian//?
>
> The debhelper documentation agrees with my experience, t
also sprach [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2004.12.14.2242 +0100]:
> Why is debhelper using debian/tmp/ as build directory, instead of
> debian//?
Read the manpage about compatibility levels. I personally prefer
./tmp when building multiple binaries and ./ for single
binary packages.
>
Why is debhelper using debian/tmp/ as build directory, instead of
debian//?
The debhelper documentation agrees with my experience, that it uses
debian// by default, but one of my packages is using
debian/tmp/, without "-P" or "--tmpdir" options anywhere. Has anyone
else experienced this?
5 matches
Mail list logo