On Sunday 10 February 2008, Frans Pop wrote: > Solution I have come up with is to write a small script that will > generate the udeb: lines _after_ dh_makeshlibs has generated the basic > shlibs file. One thing I'm unsure of is whether or not I was correct in excluding shlibs files for library packages like: - on amd64: libc6-i386 - on i386: libc6-amd64, libc6-i686, libc6-xen Can other udebs be built using those or not? If they can, then the solution is probably to just chop off the second part of the package name when determining the udeb name. Cheers, FJP
Attachment:
signature.asc
Description: This is a digitally signed message part.