<div dir="ltr">On 23 October 2013 19:58, Alec Leamas <span dir="ltr"><<a href="mailto:leamas.alec@gmail.com" target="_blank">leamas.alec@gmail.com</a>></span> wrote:<br>
<div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>On 2013-10-23 19:22, Simone Caronni wrote:<br>
</div>
I wonder if the simple answer is just "No, you can't" . OTOH, isn't it perfectly viable to install a 32-bit package on a x86_64 host using e. g., yum install steam.i386?</blockquote><div><br></div><div>
It can be done, but installing it by calling "steam.i686" or just "steam" is the same if the i686 package is the only one in the repository. It's managed by yum, ff there's the native arch package, that is pulled in, otherwise the compatible others.<br>
<br>Actually, if you run my repository on x86_64 and issue a "yum install steam" the steam.i686 package is installed.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
If that is seen as a little awkward, one could probably create subpackages with correct architecture which pulls in steam.i386 (?)<span><font color="#888888"><br></font></span></blockquote><div><br>Creating a 64 bit steam package, with all libraries and programs written
in as library(x86-32) in the requirements is a really ugly hack... I would rather not do
it. On top of this, after installing the Steam client, there are "hints"
(libraries, a stub Ubuntu runtime, etc.) that the client will sooner or
later ported to 64 bit (maybe in the new SteamMachines?); so creating a package like that would create a
lot of mess. Example:<br><br>[slaanesh@3zpc0560 Steam]$ ls -ald ubuntu12_*<br>drwx------. 2 slaanesh slaanesh 4096 Oct 20 19:57 ubuntu12_32<br>drwxrwxr-x. 2 slaanesh slaanesh 4096 Oct 10 23:37 ubuntu12_64<br>[slaanesh@3zpc0560 Steam]$ ls -al ubuntu12_64/<br>
total 15460<br>drwxrwxr-x. 2 slaanesh slaanesh 4096 Oct 10 23:37 .<br>drwx------. 26 slaanesh slaanesh 4096 Oct 23 16:37 ..<br>-rwxrwxr-x. 1 slaanesh slaanesh 472576 Oct 4 02:47 crashhandler.so<br>-rwxrwxr-x. 1 slaanesh slaanesh 173323 Sep 27 19:57 gameoverlayrenderer.so<br>
-rwxrwxr-x. 1 slaanesh slaanesh 191997 Sep 25 23:57 libtier0_s.so<br>-rwxrwxr-x. 1 slaanesh slaanesh 235937 Oct 4 02:47 libvstdlib_s.so<br>-rwxrwxr-x. 1 slaanesh slaanesh 14739300 Oct 9 04:25 steamclient.so<br>[slaanesh@3zpc0560 Steam]$ ldd ubuntu12_64/steamclient.so <br>
linux-vdso.so.1 => (0x00007fff6673c000)<br>[...]<br> libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f1d8cbb3000)<br> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1d8c997000)<br> /lib64/ld-linux-x86-64.so.2 (0x00000034b0600000)<br>
libc.so.6 => /lib64/libc.so.6 (0x00007f1d8c5d5000)<br>[...]<br><br>
Anyway, to pull in steam.i386, the steam.i386 package would need to be in the repository as well, so the problem is the same. I think the best and cleanest way is to create an i686 package and installing it as it should. Getting to something like ELRepo nvidia packages with a "nvidia-x11-drv-libs-32bit.x86_64" package containing i686 libraries is a really, really ugly thing and I would rather not do it...<br>
<br></div><div>Leaving it as is and simply adding x86_64 to ExclusiveArch would allow us to rebuild the package as normal.<br></div><div>
<br></div><div>Regards,<br></div><div>--Simone<br><br></div></div><br><br clear="all"><br>-- <br>
<div dir="ltr">You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson).<br><br><a href="http://xkcd.com/229/" target="_blank">http://xkcd.com/229/</a><br><a href="http://negativo17.org/" target="_blank">http://negativo17.org/</a><br>
</div>
</div></div>