On pe, 01 syys 2017, Neal Gompa wrote:
On Fri, Sep 1, 2017 at 7:52 AM, Marius Vollmer
<marius.vollmer@xxxxxxxxxx> wrote:
Neal Gompa <ngompa13@xxxxxxxxx> writes:
So, what about creating a dedicated appstream-data-server package that
carries only those components that we want to see on a Server?
Initially, it would contain only components of type "addon" that extend
"cockpit.desktop", and components of type "service".
Please don't do this.
What should I be doing instead? Nothing? :-)
Implement your AppStream filter at the application level, rather than
messing with appstream-data package. That makes it more portable and
won't do dumb things. We already ship the appstream-data package in
the Workstation Edition and on all the spins, so just add it to the
Server Edition if it isn't already there.
$ rpm -qi appstream-data|egrep '(Name|Version|Release|Size)'
Name : appstream-data
Version : 26
Release : 14.fc26
Size : 15631111
This is what Marius is talking about -- there is little insentive to
install 15MiB of data largely unused on Fedora Server if all you'd need
is a ~1KiB.
Filtering this information on the application side is OK if it would
have been not so useless in the Server installs.
--
/ Alexander Bokovoy
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
