| |||||||||||||
Why Steam on Linux matters for non-gamersWhy Steam on Linux matters for non-gamersPosted Sep 22, 2013 21:21 UTC (Sun) by lsl (subscriber, #86508)In reply to: Why Steam on Linux matters for non-gamers by khim Parent article: Why Steam on Linux matters for non-gamers
> If you don't care about version of the software then why would you want to track it at all?
Uhm, I wrote that. I want a somewhat recent version that gets bugfixes and new features. If I just install something from upstream one time and then forget about it I don't have that. Aside from that 'yum install gimp' (which gives me 2.8.6, btw) is much more convenient than installing GIMP from upstream.
> Something like monolithic Android release will work just as well.
I don't understand what you mean here. Who is going to create a monolithic release image with all the programs I want to use? The result of just stuffing a whole distro archive with >10k packages into some image isn't going to be acceptable to most people.
(Log in to post comments)
Why Steam on Linux matters for non-gamers Posted Sep 22, 2013 21:32 UTC (Sun) by khim (subscriber, #9252) [Link] The result of just stuffing a whole distro archive with >10k packages into some image isn't going to be acceptable to most people. Why would you want to stuff >10k packages in the image? You only need to include libraries with enough users. If there are 2-3-5 packages which need a particular library they can carry it with them, it's not a big deal. This simple procedure will shrink you list from >10k packages to 300-500 packages (or may be even less), which can easily be included in a single image. Programs themselves can come from program authors: somehow it works for MacOS, Windows, Android and iOS, why wouldn't it work for Linux?
|
|||||||||||||