Re: buildpackage doesn't put compiled files into .deb
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?
You can either change your code to use a target directory of
debian/bsf/usr/share/java, or use DH_COMPAT=1, or do something a bit more
complicated like:
# This is the debhelper compatability version to use.
export DH_COMPAT=2
firstdir := $(shell sed -n 's/Package: \(.*\)/\1/p' debian/control | head
-1)
and then use a target of debian/$(firstdir)/usr/share/java
YA
> From: Aaron Brashears <gila@gila.org>
> Date: Fri, 27 Oct 2000 21:08:41 -0700
> To: Debian Mentors <debian-mentors@lists.debian.org>
> Subject: buildpackage doesn't put compiled files into .deb
> Resent-From: debian-mentors@lists.debian.org
>
> Hi there. I'm on the road to packaging a lot of stuff. Since I'm brand
> new to being a maintiner, I'm too chicken to post an ITP. Right now,
> I've almost packaged the bean scripting framework from ibm. However,
> I'm running into a small problem.
>
> I modified debian/rules to call ant with a target directory of
> debian/tmp/usr/share/java and bsf.jar is correctly built there, but
> sadly, the jar file is never packed into the .deb file. 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 directory, but now it looks like it should be
> debian/<project-name>. Can anyone help?
>
> for info about bsf:
> http://oss.software.ibm.com/developerworks/opensource/bsf/index.html
>
> Thanks
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: