WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: SCE extensions vs. Snaps?  (Read 595 times)

Offline pq5190362

  • Full Member
  • ***
  • Posts: 205
SCE extensions vs. Snaps?
« on: November 29, 2016, 03:50:05 PM »
Hi,

aren't SCE extensions pretty much the same as Snaps:

http://snapcraft.io/

?

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9244
Re: SCE extensions vs. Snaps?
« Reply #1 on: November 29, 2016, 04:50:13 PM »
Actually not at all aside from containing needed files in one extension file if that is what snap does.  In an sce the files contained inside it's file structure are symlinked into the live filesystem just the same as if each Debian package was made into a tcz. 

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1540
Re: SCE extensions vs. Snaps?
« Reply #2 on: November 29, 2016, 05:10:36 PM »
If I'm not confusing Snap with something else, the idea is to provide packages that can run on several distros, independent from what is actually installed in the system. Meaning Snap packages contain pretty much everything the respective software depends on, which needs a fair amount of extra storage.
As I have learned recently (iirc), dCore's SCEs don't create that extra data bloat.
Download a copy and keep it handy: Core book ;)

Offline pq5190362

  • Full Member
  • ***
  • Posts: 205
Re: SCE extensions vs. Snaps?
« Reply #3 on: November 30, 2016, 02:58:32 AM »
Meaning Snap packages contain pretty much everything the respective software depends on, which needs a fair amount of extra storage.
As I have learned recently (iirc), dCore's SCEs don't create that extra data bloat.

From the dCore Wiki:

What is an SCE?

An SCE (self-contained extension) consists of a converted Debian package and all it's dependencies, packed into it's own file system and compressed into a single file (SquashFS).

That SCE description sounds very similar to how you've just described a Snap package.

Offline pq5190362

  • Full Member
  • ***
  • Posts: 205
Re: SCE extensions vs. Snaps?
« Reply #4 on: November 30, 2016, 04:15:22 AM »
Even better:

What is a snap?

A snap :
  • is a squashFS filesystem containing your app code and a snap.yaml file containing specific metadata. It has a read-only file-system and, once installed, a writable area.
  • is self-contained. It bundles most of the libraries and runtimes it needs and can be updated and reverted without affecting the rest of the system.
  • is confined from the OS and other apps through security mechanisms, but can exchange content and functions with other snaps according to fine-grained policies controlled by the user and the OS defaults.

vs.

What is an SCE?

An SCE (self-contained extension) consists of a converted Debian package and all it's dependencies, packed into it's own file system and compressed into a single file (SquashFS).

Doesn't that sound pretty much like as if Snaps and SCEs would pretty much be exactly the same?

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1540
Re: SCE extensions vs. Snaps?
« Reply #5 on: November 30, 2016, 06:26:49 AM »
But SCE don't contain "libraries and runtimes" foreign to the system.
Download a copy and keep it handy: Core book ;)