On Fri, Oct 27, 2000 at 09:28:47PM -0700, Yves Arrouye wrote:
> > Is anyone on the new-maint guide bit? I wouldn't remember offhand if
> > DH_COMPAT=1 is deprecated for new packages now.
>
> Something that is confusing for maintainers new to debhelper and that use
> dh_make, is that the new mainta
On Fri, Oct 27, 2000 at 09:28:47PM -0700, Yves Arrouye wrote:
> > Is anyone on the new-maint guide bit? I wouldn't remember offhand if
> > DH_COMPAT=1 is deprecated for new packages now.
>
> Something that is confusing for maintainers new to debhelper and that use
> dh_make, is that the new maint
On Sun, 29 Oct 2000, Britton wrote:
> > in it. See debhelper(1). If DH_COMPAT is 1, then debian/tmp is used. If
> > DH_COMPAT is 2, then debian/ is
> > used. I guess your control file has a single package, bsf?
>
> Out of curiosity, anyone know why this change?
It's pretty obvious I guess, sorr
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/ is
> used. I guess your control file has a single package, bsf?
Out of curiosity, a
On Sun, 29 Oct 2000, Britton wrote:
> > in it. See debhelper(1). If DH_COMPAT is 1, then debian/tmp is used. If
> > DH_COMPAT is 2, then debian/ is
> > used. I guess your control file has a single package, bsf?
>
> Out of curiosity, anyone know why this change?
It's pretty obvious I guess, sor
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/ is
> used. I guess your control file has a single package, bsf?
Out of curiosity,
> Is anyone on the new-maint guide bit? I wouldn't remember offhand if
> DH_COMPAT=1 is deprecated for new packages now.
I am not on the new-maint guide bit, but here's what debhelper(1) says:
V1 Setting DH_COMPAT=1 (or leaving it unset)
causes debhelper
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/ is
used. I guess your control file has a single package, bsf?
You can either change your code to use a target directory of
debian/bsf/usr/
Aaron Brashears writes:
> I checked the file system, and found that dpkg-buildpackage created
> a debian/bsf (the project name) directory which contains all the
> file that end up in the final .deb file.
>
> What's going on? The maint guide indicates that debian/tmp is
> supposed to be the install
> Is anyone on the new-maint guide bit? I wouldn't remember offhand if
> DH_COMPAT=1 is deprecated for new packages now.
I am not on the new-maint guide bit, but here's what debhelper(1) says:
V1 Setting DH_COMPAT=1 (or leaving it unset)
causes debhelper
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/ is
used. I guess your control file has a single package, bsf?
You can either change your code to use a target directory of
debian/bsf/usr
Aaron Brashears writes:
> I checked the file system, and found that dpkg-buildpackage created
> a debian/bsf (the project name) directory which contains all the
> file that end up in the final .deb file.
>
> What's going on? The maint guide indicates that debian/tmp is
> supposed to be the instal
12 matches
Mail list logo
