On Wed, Feb 14, 2018 at 03:52:06PM -0500, Owen Taylor wrote:
While waiting on/working on getting Flatpaks building in the Fedora
infrastructure, I took some time to write a tool to collect information
about applications we might want to package as Flatpaks and how they
correlate with the runtime. You can find the result at:
https://fishsoup.net/misc/flatpak-runtime-reports/applications.html
Thanks Owen. This is super-interesting!
* I'm not sure yet whether a "flatpak-shared-deps"
module with
dependencies built into /app is useful. The pros of it are:
- Things built in it will be shared on disk between different apps because
of ostree deduplication. (But not when downloading via OCI.)
- Things that are hard to build (think perl, texlive) only need to be
worked out once.
What are the cons?
* The bulk of the runtime packages get used very broadly, but there
is a
short tail of stuff in there that *no* app requires. Some of this I've
already identified as stray and to be removed (krb5-server, say.)
Once we get the building infrastructure going, we can start picking off
some of the low-hanging fruit and looking at the harder cases.
A lot of these things -- like removing extraneous deps -- will improve
the distro in general, too.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader