>From what I read, the metrics accumulation has an option to turn off the >collection, as well as the transmission
Sent from Yahoo Mail on Android On Thu, Jul 6, 2023 at 8:53 p.m., Michael Catanzaro<mcatanz...@redhat.com> wrote: On Thu, Jul 6 2023 at 11:08:15 PM +0200, Björn Persson <bj...@xn--rombobjrn-67a.se> wrote: > As a non-user of Gnome 3 who normally never runs any Gnome 3 settings > programs, I get the impression that Fedora 40 will begin accumulating > unused metrics somewhere in the filesystem. To prevent a constantly > growing waste of storage space, I'll have to run one of two Gnome 3 > settings programs – which may or may not require starting a Gnome 3 > desktop session – and find the right switch to either turn on > uploading > or turn off collection. I'll have to remember to do that after > upgrading around a year from now, and also on any new installations in > the distant future. > > If my impression is wrong, then the change proposal needs to be > amended. Well this change proposal is for Fedora Workstation specifically. That's in the title. :) I would envision installing eos-event-recorder-daemon via a Recommends: from the gnome-control-center and gnome-initial-setup packages (and probably also by adding it to the workstation-product comps group), so if you don't have gnome-initial-setup or gnome-control-center installed, you wouldn't get in on upgrade. I'm not sure whether I want to amend this level of detail into the change proposal in case we might want to change the specifics of how it gets installed, but that's just to give you an idea of what I'm thinking currently. Certainly the metrics components should not be installed for non-GNOME users as part of this change proposal. However, I've heard that Fedora KDE might also be interested in adding metrics once we have this working in Workstation. But that would be up to the people contributing to Fedora KDE and would need to be proposed separately. I think eos-event-recorder-daemon uses some sort of ring buffer to eventually discard old events, so that storage space does not increase forever and should not become an issue? But please don't quote me on this; I have a lot of comments to respond to, and I'm not super familiar with the code, and I don't want to dive in to look at how it works right now. If there's really an issue with space growing without bound, then that's a bug we should fix, but I don't think it's so. (BTW, the GNOME 3 era concluded with the release of GNOME 40 in Fedora 34, so I wouldn't except Fedora users to still be using GNOME 3. :) Michael > _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
