[14:39] Hi, I want to include some file called "someconfig.in" in my package, which will contain a line like "my arch is @ARCH@", and the @ARCH@ will be replaced with the compile-time architecture. [14:40] The rest of the package files are in shell or python, nothing gets compiled so we're not using autotools etc yet [14:40] Where should I look? What part processes .in files? Is that autotools? [14:40] that is [14:41] Thanks, googling... :) [14:42] are you wanting to include this upstream or only in your packaging? [14:43] I'm both upstream and packager, so I guess it would be better to include it upstream [14:43] Would a simple makefile be enough, since I only want that one simple thing? [14:43] With some sed expression inside to replace ARCH? [14:43] yes [15:00] Laney: uploaded for utopic, not yet for trusty, it's pending for when I don't need the bandwidth. :) [15:12] how do you slap bzr upside the head and get it to stop unapplying quilt patches all the time? I can find nothing about bzr and quilt in the documentation or web. [15:35] * alkisg can't find an $ARCH variable in Makefiles... [15:35] If I have to find it myself with shell, dpkg --print-architecture etc, then why would I use make instead of a plain #!/bin/sh file? [15:38] it's up to you if you use a Makefile for the sed call or use a shell script to do the same [15:39] geser: not for the sed call, but for detecting the build architecture [15:40] E.g. amd64 in debian vs x86_64 in other distros [15:40] I wouldn't want to use distro-specific code there, would I? [15:41] In some distributions I would see it with `uname -m`, in debian-based distros with `dpkg --print-architecture`, but it sounds like a very common problem, I would assume a more elegant solution would be available... [16:55] Oh well, if we're going to have distro-specific code anyway to detect the target arch, we can just leave the `sed /s/@ARCH@/$ARCH/` part up to the packaging process... === Guest60657 is now known as mfisch