X-Debbugs-CC: cl...@debian.org, adcon...@0c3.net, m...@suse.de, j...@suse.cz, a...@suse.de
El dv 26 de 01 de 2018 a les 08:39 +0100, Andreas Jaeger va escriure: > No, this is not possible - it would break binary compatibility. The path > is hardcoded into each binary and if you change it, your application > will not run anywhere else, It would be nice if you answered the question about appendix A.1. So, we have five people who state or imply that either my amd64 systems do not exist or they are unavoidably incompatible with systems depending on a /lib64 directory. My systems obviously exist. To the claim that I cannot run a /lib64 program without rebuilding, the answer is easy to say: try my system. To the claim that applications from my system will not run anywhere else, I can provide a counterexample: you can install the attached package. Would you accept the evidence? Is /lib64 still a mistake or rather a maintainer's choice?
hello-nolib64_0.1_amd64.deb
Description: application/deb
hello-nolib64_0.1.tar.gz
Description: application/compressed-tar
Format: 3.0 (native) Source: hello-nolib64 Binary: hello-nolib64 Architecture: any Version: 0.1 Maintainer: Javier Serrano Polo <jav...@jasp.net> Standards-Version: 3.9.1 Build-Depends: debhelper (>= 8) Checksums-Sha1: 0cb0a6e9395ddfd9eec0694c27925a43815a2a97 9730 hello-nolib64_0.1.tar.gz Checksums-Sha256: 78b16e6c70c246a71842c5d2fb2d6ce0b963f5fa7bb1ffe28b09834758013a5e 9730 hello-nolib64_0.1.tar.gz Files: c001d3d99923344e11598a991ed878e5 9730 hello-nolib64_0.1.tar.gz
smime.p7s
Description: S/MIME cryptographic signature
