=== almaisan-away is now known as al-maisan | ||
=== al-maisan is now known as almaisan-away | ||
=== yofel_ is now known as yofel | ||
ESphynx | good evening :) | 00:54 |
---|---|---|
dholbach | good morning | 07:47 |
=== almaisan-away is now known as al-maisan | ||
=== al-maisan is now known as almaisan-away | ||
=== almaisan-away is now known as al-maisan | ||
=== dk_ is now known as Guest35783 | ||
=== al-maisan is now known as almaisan-away | ||
jariq | My package installs file into /etc directory but I need this file to have different contents on i386 arch and different contents on amd64. I am not sure how to approach this problem. Any hints? | 10:59 |
tumbleweed | why? | 11:04 |
jariq | tumbleweed: it is a configuration file that has to contain *full path* to libcrypto. Its location is /usr/lib/i386-linux-gnu/libcrypto.so on i386 and /usr/lib/x86_64-linux-gnu/libcrypto.so on amd64. | 11:11 |
funkyHat | jariq: why are you not relying on the linker to find libcrypto for you? | 11:16 |
jariq | funkyHat: I would in general but it is LoadFile directive of Apache HTTPD that requires "absolute path or relative to ServerRoot" and patching httpd to rely on linker is no go here. | 11:22 |
jariq | So I was thinking about using "if" statement with architecture (or something similar) in rules file, but I was unable to find an example or any documentation that would support this idea. | 11:24 |
funkyHat | jariq: if you really need to hard code the path to libcrypto and include it in httpd config, why not include a file outside of /etc instead, and build different packages for each arch? I'm sure there is a less weird way of going about this whole thing though | 11:30 |
jariq | funkyHat: Could you please elaborate on "different packages for each arch"? Package with different name? | 11:44 |
tumbleweed | jariq: ok, so assuming this is a good idea, what's the problem? just generate the file during the build | 11:47 |
funkyHat | ^this | 11:47 |
geser | jariq: you build a package for each arch ("Architecture: any" in debian/rules) and not an Arch:all package | 12:08 |
tumbleweed | or, I suppose, you generate the config file in postinst, but failure in maintainer scripts breaks users' systems... | 12:10 |
funkyHat | And users that use puppet or copy config files to a new system or migrate from 32bit to 64bit systems have problems too, which is where my suggestion stemmed from. | 12:13 |
jariq | Generating the file during the build: How do I know in rules file for which platform is it building? is there any variable I can test? | 12:16 |
jariq | Different package for different platform: Is there any convention on naming resulting packages? I.e package32 for i386 and package64 for amd64? | 12:18 |
tumbleweed | jariq: you run dpkg-architecture -qDEB_BUILD_MULTIARCH | 12:23 |
tumbleweed | jariq: no, the package is the same name for all architectures | 12:23 |
tumbleweed | obviously the bash package on amd64 has a different binary for /bin/bash, as the bash package on i386 | 12:24 |
jariq | I am going to give a try to dpkg-architecture. Thank you for suggestions. | 12:26 |
tumbleweed | oops, I meant DEB_HOST_MULTIARCH | 12:27 |
jariq | tumbleweed: DEB_HOST_MULTIARCH works for me. Thank you very much. | 12:34 |
=== dk is now known as Guest66626 | ||
=== emma_ is now known as emma | ||
=== highvolt1ge is now known as highvoltage | ||
=== yofel_ is now known as yofel | ||
=== nenolod is now known as mogri | ||
ESphynx | xnox: Thanks for getting .05 in =) | 21:43 |
xnox | ESphynx: note the bug report I filed though ;-) | 23:49 |
ESphynx | xnox: noted ;) | 23:50 |
ESphynx | xnox: I promise to do it for next update :P | 23:50 |
ESphynx | xnox: btw that's not new with this package, but I guess you caught it cause I took out the giflib-dev build dep :P | 23:50 |
ESphynx | (which wasn't used) | 23:50 |
xnox | ESphynx: I'm not gonna tell you how/why I spotted it, just to keep you in the dark and myself on the edge ;-) | 23:51 |
xnox | that should keep you more disciplined =))))))) in an nice way. | 23:51 |
ESphynx | lol | 23:51 |
ESphynx | as for taking out the deps folder, well again I'm ok with it for the orig tarball | 23:52 |
ESphynx | but not for the tarball that you'd be grabbing off the GitHub tag | 23:52 |
ESphynx | (like the other few things taht are already 'omitted' in the debian .orig tarball) | 23:52 |
ESphynx | that's fine? | 23:53 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!