On Tue, Feb 04, 2014 at 01:34:19AM +0900, Osamu Aoki wrote: > I recently packaged a package with custom *-config and hit by multiarch > bug for -dev package like this one immediately after my upload (Jakub, > thanks for checking it). > > kakasi http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737378 > > Since this was caused by hardcoding @libdir@ path into shell code, > I replaced that @libdir@ part of code with > > /usr/lib/$(dpkg-architecture -qDEB_HOST_MULTIARCH) > ^^^^ > I know I solved issue for normal build case and possibly for cross > compile. > > Colin, what do you think of such a fix.
I'm afraid I generally think this approach is inappropriate, since *-config scripts are intended for use beyond just building packages. There's a risk that people building other kinds of source tree against *-config scripts that have been hacked in this way would have their setups broken by such changes. Perhaps you could test whether dpkg-architecture exists, and if it doesn't then you could fall back to @libdir@. It still seems like a bit of a layering violation to me, but you might get away with it with that modification. Cheers, -- Colin Watson [[email protected]] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
