<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Flatpak, Appimage And Snap &#8211; How Do They Stack?	</title>
	<atom:link href="https://www.geeksmint.com/flatpak-appimage-and-snap-how-do-they-stack/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.geeksmint.com/flatpak-appimage-and-snap-how-do-they-stack/</link>
	<description>GeeksMint: Computers, How-to&#039;s, Internet, Tips and Tricks</description>
	<lastBuildDate>Wed, 17 Apr 2019 06:59:16 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Ben Guy-Williams		</title>
		<link>https://www.geeksmint.com/flatpak-appimage-and-snap-how-do-they-stack/#comment-4058</link>

		<dc:creator><![CDATA[Ben Guy-Williams]]></dc:creator>
		<pubDate>Wed, 17 Apr 2019 06:59:16 +0000</pubDate>
		<guid isPermaLink="false">https://www.geeksmint.com/?p=1115#comment-4058</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.geeksmint.com/flatpak-appimage-and-snap-how-do-they-stack/#comment-2871&quot;&gt;nigra truo&lt;/a&gt;.

It was badly phrased.
&#039;Package can be freely developed without causing a conflict on your system, reducing the risk of breaking... but at the expense of using disk space to store it&#039;s own set of libraries and files&#039; might have been better.

Something I never stopped missing was the ability to find an application, download it and run it (with Windows). With Linux, you find your .deb, try an install then it fails because &#039;lib.so&#039; is now version 4 but this package wants version 3... so it fails.

The snap/appimage etc actually do use more filesystem space but allow developers to give us something that can run with the newest available library at the time of creation, not necessarily the one available in our system and without the need to use a PPA to upgrade the system (and probably break something else at the same time).

I find synaptic/apt/PPA to be lacking in many areas - brilliant, but also lacking - and totally see the need to add a choice of an &#039;executive&#039; file.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a target="_blank" href="https://www.geeksmint.com/flatpak-appimage-and-snap-how-do-they-stack/#comment-2871">nigra truo</a>.</p>
<p>It was badly phrased.<br />
&#8216;Package can be freely developed without causing a conflict on your system, reducing the risk of breaking&#8230; but at the expense of using disk space to store it&#8217;s own set of libraries and files&#8217; might have been better.</p>
<p>Something I never stopped missing was the ability to find an application, download it and run it (with Windows). With Linux, you find your .deb, try an install then it fails because &#8216;lib.so&#8217; is now version 4 but this package wants version 3&#8230; so it fails.</p>
<p>The snap/appimage etc actually do use more filesystem space but allow developers to give us something that can run with the newest available library at the time of creation, not necessarily the one available in our system and without the need to use a PPA to upgrade the system (and probably break something else at the same time).</p>
<p>I find synaptic/apt/PPA to be lacking in many areas &#8211; brilliant, but also lacking &#8211; and totally see the need to add a choice of an &#8216;executive&#8217; file.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: nigra truo		</title>
		<link>https://www.geeksmint.com/flatpak-appimage-and-snap-how-do-they-stack/#comment-2871</link>

		<dc:creator><![CDATA[nigra truo]]></dc:creator>
		<pubDate>Tue, 21 Mar 2017 05:29:17 +0000</pubDate>
		<guid isPermaLink="false">https://www.geeksmint.com/?p=1115#comment-2871</guid>

					<description><![CDATA[Quote:
-----------
In this way, a package does not cause a clutter on your system reducing the risk of breaking the rest of your Linux system.
-----------
You know if clutter means redundant, doubled and quadrupled files and instead of all like type files (like libraries) in their proper folder, snap / flatpak / appimage does exactly the opposite of what they should do, create clutter. Packaging systems like RPM and DEB by the way are EXACTLY designed to not break the system, they will never overwrite an existing lib or file that is owned by another program, thus increasing stability of the system. I&#039;m curious how the experiment will go, especially snap, since all tools will come in that format. Shared libraries will no longer be shared, package sizes will skyrocket, updates will take a lot longer and generally RAM usage will go up. Will it go up to the level of Windows, where you can barely run the OS with 2 or 4 GBs? Time will tell.
I think it is great to have apps that run everywhere, but having the whole OS like this might be a really bad idea. I doubt that a Linux that is built as such would be able to run on 512 MB or 1 GB of Ram like the Raspberrry Pi (like Windows as an example cannot). I wish there was an easy workable way to use statically linked DEBs and RPMs, because.... that would EXACTLY solved this problem, with a well established super stable packaging system, instead of having to create a new one (or in this case, 4 of them)]]></description>
			<content:encoded><![CDATA[<p>Quote:<br />
&#8212;&#8212;&#8212;&#8211;<br />
In this way, a package does not cause a clutter on your system reducing the risk of breaking the rest of your Linux system.<br />
&#8212;&#8212;&#8212;&#8211;<br />
You know if clutter means redundant, doubled and quadrupled files and instead of all like type files (like libraries) in their proper folder, snap / flatpak / appimage does exactly the opposite of what they should do, create clutter. Packaging systems like RPM and DEB by the way are EXACTLY designed to not break the system, they will never overwrite an existing lib or file that is owned by another program, thus increasing stability of the system. I&#8217;m curious how the experiment will go, especially snap, since all tools will come in that format. Shared libraries will no longer be shared, package sizes will skyrocket, updates will take a lot longer and generally RAM usage will go up. Will it go up to the level of Windows, where you can barely run the OS with 2 or 4 GBs? Time will tell.<br />
I think it is great to have apps that run everywhere, but having the whole OS like this might be a really bad idea. I doubt that a Linux that is built as such would be able to run on 512 MB or 1 GB of Ram like the Raspberrry Pi (like Windows as an example cannot). I wish there was an easy workable way to use statically linked DEBs and RPMs, because&#8230;. that would EXACTLY solved this problem, with a well established super stable packaging system, instead of having to create a new one (or in this case, 4 of them)</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Alexandru Băluț		</title>
		<link>https://www.geeksmint.com/flatpak-appimage-and-snap-how-do-they-stack/#comment-2512</link>

		<dc:creator><![CDATA[Alexandru Băluț]]></dc:creator>
		<pubDate>Wed, 27 Jul 2016 15:05:00 +0000</pubDate>
		<guid isPermaLink="false">https://www.geeksmint.com/?p=1115#comment-2512</guid>

					<description><![CDATA[&quot;With Ubuntu Snap software packing format already being used on many Linux distributions&quot; - What does that even mean?
Would be nice to know how Snap and Flatpak can exist at the same time on the computer.]]></description>
			<content:encoded><![CDATA[<p>&#8220;With Ubuntu Snap software packing format already being used on many Linux distributions&#8221; &#8211; What does that even mean?<br />
Would be nice to know how Snap and Flatpak can exist at the same time on the computer.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
