Le 5/4/21 à 3:37 PM, Toomas Soome via openindiana-discuss a écrit :
Well you can *update* packages and remain in same OS version. Or,
you can *upgrade* to next OS version, for example from Ubuntu 16
to Ubuntu 17. In that case yes, breaks happen, and most users
prefer to simply reinstall instead of upgrading, which they
consider cleaner.
Well, with upgrade you get new OS version [...] because you have technical
changes which are either not compatible with current apps or introduce some
major (new) technologies into the system.
But when our interfaces remain stable and we do not break the apps and we do
not have marketing department… we can just update. But then again, things are
never that simple;)
I am beginning to appreciate a little more how containers fix this
compatibility issue.
The only thing I need to figure out is how to get the most out of
containers
optimisation-wise, i.e still getting a way to share common libraries
between
same-generation apps. Otherwise, I see software distribution going full
circle
+-----------------------------------+
+>>>>>>>>>>>>+Every software uses its own library+>>>>>>>>>>+
snap, docker, virtual ^
+-----------------------------------+ v
environements, appImage,
^ v
Introducing shared libraries
whole VMs. ^ v
+----------+---------------------------+
+----------------------v-------------+
|This particular software needs lib L | |
Let's have common code in shared |
|version 2 but your system relies on | |
libraries, this should make apps |
|lib L version 1. | | smaller in size and
easier to |
+----------^---------------------------+ |
maintain. |
^ +----------------------+-------------+
^ v
+<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+
Can't have
multiple versions
of same lib
-- Yassine.
_______________________________________________
openindiana-discuss mailing list
[email protected]
https://openindiana.org/mailman/listinfo/openindiana-discuss
