| Summary: | Install kdegraphics-thumbnailers by default | ||
|---|---|---|---|
| Product: | [KDE Neon] neon | Reporter: | Nate Graham <nate> |
| Component: | general | Assignee: | Neon Bugs <neon-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | jr, neon-bugs-null, sitter |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Nate Graham
2018-08-21 15:48:24 UTC
I think we are doing a poor job of encoding runtime usefulness via cmake. plasma-desktop likely should cmake runtime indicate on dolphin. And dolphin should cmake runtime indicate on kio-extras and kdegraphics-thumbernailers? Or maybe we should throw it in a wiki? Cmake certainly makes these things more obvious though. It may be worth having a discussion about this. We need a way to describe what a "good" stack lineup for a "good" plasma/apps experience looks like. We never really documented this sort of thing, so it's uniquely hard for binary packages to end up having correct "relationships" with other binary packages as that is mostly up to packagers guessing what is most useful to have out of the box. That said, I struggle to know where the thumbnailer dep should go in neon, but I agree that it should be somewhere ^^ I added this in experimentally but it's not a great implementation, it just uses an external gv command and I hear it can take lots of CPU. It would be nicer to have one using poppler or okular as more modern technology. Can this ticket gets closed? If a future version of kdegraphics-thumbnailers uses a poppler-based PDF thumbnailer, it would automatically picked up in Neon installs. Was this actually implemented by packaging it in Neon (i.e. FIXED) or deferred pending a better implementation? Yes it's pulled into the ISO and default install by neon-desktop Great, thanks! |