On Wed, Feb 27, 2019 at 02:08:29PM -0300, Andreas Hasenack wrote:
> I'm working on the talloc package, and it installs this file when
> building python3 bindings:
> I can't put that literally in a d/<pkg>.install file, because of the
> architecture. The path component after usr/lib can be replaced by "*",
> but using "*" for the bit in the filename seems it could match
> something else by mistake:
> So I thought about using dh-exec, just like
> suggests, but that didn't work.
> The silly problem is that the triplet x86_64-linux-gnu as a directory
> is not the same triplet used in the filename: x86_64-linux-gnu !=
> x86-64-linux-gnu ("-" vs "_")
> Is there a neat solution to this, other than using "*" for the architecture?
No, since x86-64-linux-gnu is not a standard name for the architecture. I
would suggest that you instead simply use the dh-exec substitution for the
first part of the path, and a glob for the second:
That should minimize any false-positive matches of the glob.
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/