[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#5044: dpkg-buildpackage and dpkg-source don't agree on what's required in a package



-----BEGIN PGP SIGNED MESSAGE-----

Package: dpkg-dev
Version: 1.4.0.3

dpkg-buildpackage should at least give a warning when building a diff
file that will be unbuildable by dpkg-source.

I've created various *.ph files for perl and included them in the perl
package since this was a simple and elegant solution.  They just get
installed in the right place.  Unfortunately, dpkg-source -x dies when
it goes to unpack the subdirs of the *.ph tree.

On a second, somewhat related note that is nowhere near as important.
If I have to split the *.ph files out into their own package, dpkg
forces it to be a arch-dependent target since the directory all the
files are in is /usr/lib/perl5/${archname}-linux/5.00307.  I don't have
a problem with messing with a symlink or two in the postinst/prerm but
it seems to defeat the purpose of dpkg to copy a whole tree to a new
location but it's painful for this package to be arch-dependent on a
directory name.  (No, I can't just use a symlink since there can be
other stuff there that really is arch-dependent.)

Darren
- -- 
<torin@daft.com> <http://www.daft.com/~torin> <torin@debian.org> <torin@io.com>
Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996
@ Do you have your clothes on? I probably don't. Take yours off. Feel better. @
@ Sysadmin, webweaver, postmaster for hire.  C/Perl/CGI programmer and tutor. @

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBMnWBZ44wrq++1Ls5AQGumwP+Pc3SmxVbsEZ7U8Z1vGVGIkIgHc0JJ8++
/AMYpmlBS5g1WRDclveP/tBq0EFatIWXcgCO4M7s18rdOY8VjpNZU385pxY3Ek28
Nc7YTaga+D6D9dgzjzflJX8KNAoOD/v1EeRcZIch7xsve6zZvK4HVPtV/loUsVHq
Y5qGgkvxbZY=
=WDB8
-----END PGP SIGNATURE-----

--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com


Reply to: