| Summary: | KUserFeedback components are hard (not optional) runtime dependency once compiled in | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kuserfeedback | Reporter: | grizzlyuser <grizzlyuser> |
| Component: | Telemetry Provider | Assignee: | Volker Krause <vkrause> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | nate |
| Priority: | HI | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
grizzlyuser
2020-05-03 15:01:50 UTC
I agree that they should be runtime dependencies, not compile-time dependencies, for just this reason. Removing kuserfeedback from your system shouldn't blow away your apps! Not practically doable, at best you could move the actual submission to a small plugin, but that still keeps the bulk of the framework compile-time. That's disappointing. I predict that we will continue to receive complaints from a minority of vocal users about this until we come up with a way for it to be removed at runtime. |