Re: buildpackage doesn't put compiled files into .deb

To: Yves Arrouye <yves@realnames.com>
Cc: Aaron Brashears <gila@gila.org>, Debian Mentors <debian-mentors@lists.debian.org>
Subject: Re: buildpackage doesn't put compiled files into .deb
From: Britton <fsblk@aurora.uaf.edu>
Date: Sun, 29 Oct 2000 01:53:14 -0800 (AKDT)
Message-id: <[🔎] Pine.OSF.4.21.0010290152260.11551-100000@aurora.uaf.edu>
In-reply-to: <[🔎] B61FA2B3.19265%yves@realnames.com>

On Fri, 27 Oct 2000, Yves Arrouye wrote:

> My guess is that your rules file has:
> 
> export DH_COMPAT=2
> 
> in it. See debhelper(1). If DH_COMPAT is 1, then debian/tmp is used. If
> DH_COMPAT is 2, then debian/<name of the first package in debian/control> is
> used. I guess your control file has a single package, bsf?

Out of curiosity, anyone know why this change?

Reply to:

Follow-Ups:
- Re: buildpackage doesn't put compiled files into .deb
  - From: Britton <fsblk@aurora.uaf.edu>

References:
- Re: buildpackage doesn't put compiled files into .deb
  - From: Yves Arrouye <yves@realnames.com>

Prev by Date: Re: License issue
Next by Date: Re: buildpackage doesn't put compiled files into .deb
Previous by thread: Re: buildpackage doesn't put compiled files into .deb
Next by thread: Re: buildpackage doesn't put compiled files into .deb
Index(es):
- Date
- Thread