repackage of asterisk-1.4.17~dfsg not working

[Brian J. Murrell]

Hello,

I'm trying to simply repackage asterisk-1.4.17~dfsg as downloaded from
Hardy.  It simply does not work.  It simply cannot work the way the
debian/rules file was written.

Take for example this little bit from the rules file:

install-indep: build-indep
	dh_testdir
	dh_testroot
	dh_clean -k -i
	dh_installdirs -i

	$(FETCH_ENV) $(MAKE) $(BUILDFLAGS) DESTDIR=$(CURDIR)/debian/tmp install samples

	dh_install -i --sourcedir=debian/tmp

I really cannot see how this is supposed to actually work.  The "make
DESTDIR=$(CURDIR)/debian/tmp install samples" will do a full asterisk
install as well as install sample files into debian/tmp.  However the
directories "make install" expects to exist under debian/tmp won't
actually be there because the prior "dh_installdirs -i" will create them
in debian/asterisk (debian/compat == 5).

Furthermore, most of the directories "make install" expects to be there
(i.e. usr/sbin) won't even be there because they are created by
"dh_installdirs -s", not "dh_installdirs -i".

So here's the hacks I had to make to the rules file to get the instal-*
targets to work correctly:

install-arch: build-arch
	dh_testdir
	dh_testroot
	dh_clean -k -s
	DH_COMPAT=1 dh_installdirs -s
	
	$(FETCH_ENV) $(MAKE) $(BUILDFLAGS) DESTDIR=$(CURDIR)/debian/tmp install

	dh_install -s --sourcedir=debian/tmp

	$(RM) -f $(CURDIR)/debian/asterisk/usr/sbin/{stereorize,streamplayer}
	touch $@

install-indep: build-indep
	dh_testdir
	dh_testroot
	dh_clean -k -i
	DH_COMPAT=1 dh_installdirs -s
	DH_COMPAT=1 dh_installdirs -i

	$(FETCH_ENV) $(MAKE) $(BUILDFLAGS) DESTDIR=$(CURDIR)/debian/tmp install samples

	dh_install -i --sourcedir=debian/tmp

	install -m 0644 -D $(CURDIR)/debian/asterisk-config.lintian-overrides \
		$(CURDIR)/debian/asterisk-config/usr/share/lintian/overrides/asterisk-config

Yes, indeed, very ugly hacks.  But given the way those targets were
written, that is the only way on my Hardy system to make a
dpkg-rebuildpackage actually work.

I cannot imagine this rules file as shipped in Hardy actually works.
How did y'all manage to create binary packages from it?

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/ubuntu-motu/attachments/20080504/873d435b/attachment.pgp