On Sun, Jul 9, 2017 at 6:46 PM, Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: > Jaroslav Reznik wrote: >> = System Wide Change: Graphical Applications as Flatpaks = >> https://fedoraproject.org/wiki/Changes/Graphical_Applications_as_Flatpaks >> >> Change owner(s): >> * Owen Taylor <otaylor@xxxxxxxxxx> > > This change is leaving several questions unanswered: But... it's shiny! And new! And distinct from all other packaging systems, so it won't have *any* of the problems any or all of them have shown! And if there's a conflict, overwrite, or embedded incompatible library or conflicting dependency, it will be a Simple Matter Of Programming. And it could not possibly run into any of those more difficult already documented and partially addressed conflicts because, hey, it's *new* and people will stop using the other tools immediately due to its obvious superiority! Sorry, but I've been seeing these kinds of issues for a long time. pkg, apt, rpm, VM images, docker, chroot cages, encap, pyvenv, and associated build tools such as autoconf, CPAN, pip, ant, maven, and gradle. I still see a lot of inevitable and unavoidable conflicts between system libraries published with RPM and flatpack bundled graphical packages. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
