I still don't get the whole thing (vs static + dynamic linking). It all seems so difficult and complex. Why not just...

  • want a specific version of libfox? -> statically link libfox v6.9
  • want per-interface permissions? -> make a new dynamic linker that prompts the user, "do you want to allow this app to access libfox? yes/no" OR have the linker read declarations at package time (allow/deny/ask).
  • want a unified api? -> make a new shared library

(1/?)

@foxxy

Dependency tree of packages: they must be integrated, only one version of libraries, some software can't be packaged, some combination of packages are not allowed.

All-in-one bundles: not feasible to maintain the libraries updated, huge security risks and more resources used.

OSTree deployments: make different version of every kind of file available to different processes but deduplicate the storage by storing only the diff.

(and Flatpak has a sandbox, permissions system etc...)

Follow

@alxlg De-duplicating statically linked libraries in apps would be difficult without a Flatpak style package format, good point.

· · 0 · 0 · 1
Sign in to participate in the conversation
Critter Camp - Mastodon

This server is part of a collection of services that are mostly federated and run by a couple of furries.