5:22 p.m.
Hello,
the Steam review has been taken, however the reviewer wonders if the
infrastructure can cope with i686 binary packages being pushed to the
x86_64 repository. I thought it was possible, but this is my first review
in RPMFusion so I don't know details of the infrastructure.
When installing in a x86_64 system, the package pulls in the correct 32 bit
dependencies. Currently I'm using Steam with 65 games on a 64 bit Fedora 19
host.
The same package is the currently suggested one [1] from Valve for running
Steam on both i386 and x86_64 hosts. The package was created by me and
adjusted based on feedback from the Steam community forum with users
providing additional information and testing pulling from my personal
repository page [2]. In fact, 99% of the users run a 64 bit distribution.
It would be a shame not to see this appear in RPMFusion just for a limit of
the infrastructure.
Can the i686 be pushed also to the x86_64 repository once reviewed?
Thanks & regards,
--Simone
[1] https://developer.valvesoftware.com/wiki/Steam_under_Linux#Fedora
[2] http://negativo17.org/steam/
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
http://xkcd.com/229/
http://negativo17.org/
5:58 p.m.
On 2013-10-23 19:22, Simone Caronni wrote:
Hello,
the Steam review has been taken, however the reviewer wonders if the
infrastructure can cope with i686 binary packages being pushed to the
x86_64 repository. I thought it was possible, but this is my first
review in RPMFusion so I don't know details of the infrastructure.
When installing in a x86_64 system, the package pulls in the correct
32 bit dependencies. Currently I'm using Steam with 65 games on a 64
bit Fedora 19 host.
The same package is the currently suggested one [1] from Valve for
running Steam on both i386 and x86_64 hosts. The package was created
by me and adjusted based on feedback from the Steam community forum
with users providing additional information and testing pulling from
my personal repository page [2]. In fact, 99% of the users run a 64
bit distribution.
It would be a shame not to see this appear in RPMFusion just for a
limit of the infrastructure.
Can the i686 be pushed also to the x86_64 repository once reviewed?
Thanks & regards,
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? If that is seen as a little awkward, one
could probably create subpackages with correct architecture which pulls
in steam.i386 (?)
--alec
6:28 p.m.
On 23 October 2013 19:58, Alec Leamas <leamas.alec(a)gmail.com> wrote:
On 2013-10-23 19:22, Simone Caronni wrote:
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?
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.
Actually, if you run my repository on x86_64 and issue a "yum install
steam" the steam.i686 package is installed.
If that is seen as a little awkward, one could probably create
subpackages
with correct architecture which pulls in steam.i386 (?)
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:
[slaanesh@3zpc0560 Steam]$ ls -ald ubuntu12_*
drwx------. 2 slaanesh slaanesh 4096 Oct 20 19:57 ubuntu12_32
drwxrwxr-x. 2 slaanesh slaanesh 4096 Oct 10 23:37 ubuntu12_64
[slaanesh@3zpc0560 Steam]$ ls -al ubuntu12_64/
total 15460
drwxrwxr-x. 2 slaanesh slaanesh 4096 Oct 10 23:37 .
drwx------. 26 slaanesh slaanesh 4096 Oct 23 16:37 ..
-rwxrwxr-x. 1 slaanesh slaanesh 472576 Oct 4 02:47 crashhandler.so
-rwxrwxr-x. 1 slaanesh slaanesh 173323 Sep 27 19:57
gameoverlayrenderer.so
-rwxrwxr-x. 1 slaanesh slaanesh 191997 Sep 25 23:57 libtier0_s.so
-rwxrwxr-x. 1 slaanesh slaanesh 235937 Oct 4 02:47 libvstdlib_s.so
-rwxrwxr-x. 1 slaanesh slaanesh 14739300 Oct 9 04:25 steamclient.so
[slaanesh@3zpc0560 Steam]$ ldd ubuntu12_64/steamclient.so
linux-vdso.so.1 => (0x00007fff6673c000)
[...]
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f1d8cbb3000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1d8c997000)
/lib64/ld-linux-x86-64.so.2 (0x00000034b0600000)
libc.so.6 => /lib64/libc.so.6 (0x00007f1d8c5d5000)
[...]
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...
Leaving it as is and simply adding x86_64 to ExclusiveArch would allow us
to rebuild the package as normal.
Regards,
--Simone
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
http://xkcd.com/229/
http://negativo17.org/
6:49 p.m.
2013/10/23 Simone Caronni <negativo17(a)gmail.com>
Hello,
the Steam review has been taken, however the reviewer wonders if the
infrastructure can cope with i686 binary packages being pushed to the
x86_64 repository. I thought it was possible, but this is my first
Hi Simone
From the plague infrastructure perspective there is no issue with
having
the i686 package automatically copied into the x86_64 repository. From the
package you will only need to use ExclusiveArch: i686
That way the package will be built only for the i686 target.
Then I will adjust the package to be copied into the x86_64 repository on
plague configuration.
This might be different with koji (where some special cases might be
handled within mash instead).
Thx for this review.
Nicolas (kwizart)
7:50 p.m.
On 23 October 2013 20:49, Nicolas Chauvet <kwizart(a)gmail.com> wrote:
From the plague infrastructure perspective there is no issue with
having
the i686 package automatically copied into the x86_64 repository. From the
package you will only need to use ExclusiveArch: i686
Quick question. I have used ExclusiveArch: %{ix86} in the package, is that
ok?
$ rpm --eval %{ix86}
i386 i486 i586 i686 pentium3 pentium4 athlon geode
Is that ok for plague?
Thanks,
--Simone
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
http://xkcd.com/229/
http://negativo17.org/
7:55 p.m.
2013/10/23 Simone Caronni <negativo17(a)gmail.com>
On 23 October 2013 20:49, Nicolas Chauvet <kwizart(a)gmail.com>
wrote:
> From the plague infrastructure perspective there is no issue with having
> the i686 package automatically copied into the x86_64 repository. From the
> package you will only need to use ExclusiveArch: i686
>
Quick question. I have used ExclusiveArch: %{ix86} in the package, is that
ok?
$ rpm --eval %{ix86}
i386 i486 i586 i686 pentium3 pentium4 athlon geode
Is that ok for plague?
No. This, in plague, will build each variant where we only wanted one of
them. (currently i686).
Nicolas (kwizart)
7:56 a.m.
Hi Nicolas,
On 23 October 2013 20:49, Nicolas Chauvet <kwizart(a)gmail.com> wrote:
From the plague infrastructure perspective there is no issue with
having
the i686 package automatically copied into the x86_64 repository. From the
package you will only need to use ExclusiveArch: i686
That way the package will be built only for the i686 target.
Then I will adjust the package to be copied into the x86_64 repository on
plague configuration.
is it normal that the steam package is available only in the i386 testing
repository? Will it be copied to x86_64 only when the package reaches
stable status?
http://download1.rpmfusion.org/nonfree/fedora/updates/testing/19/i386/
http://download1.rpmfusion.org/nonfree/fedora/updates/testing/19/x86_64/
Thanks & regards,
--Simone
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
http://xkcd.com/229/
http://negativo17.org/
12:45 p.m.
Hi Nicholas,
On 4 November 2013 08:56, Simone Caronni <negativo17(a)gmail.com> wrote:
is it normal that the steam package is available only in the i386
testing
repository? Will it be copied to x86_64 only when the package reaches
stable status?
http://download1.rpmfusion.org/nonfree/fedora/updates/testing/19/i386/
http://download1.rpmfusion.org/nonfree/fedora/updates/testing/19/x86_64/
the Steam package is availabe for Fedora 18/19/20 i686 and for Fedora 18/19
x86_64. Can you add it also the rawhide x86_64 repository?
https://bugzilla.rpmfusion.org/show_bug.cgi?id=3020
Thanks,
--Simone
--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).
http://xkcd.com/229/
http://negativo17.org/
4034
days inactive
4051
days old
rpmfusion-developers@lists.rpmfusion.org
8 comments
3 participants
participants (3)
-
Alec Leamas -
Nicolas Chauvet -
Simone Caronni