New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
evince: enable all features #58259
evince: enable all features #58259
Conversation
The postscript fix needs to be backported to the release branch as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We've began work on getting gnome 3.32 so this will conflict with that.
I don't see too much of a problem with this aside from enabling the nautilus plugin by default.
(nautilus isn't present everywhere this is used)
I'd also like to enable meson for this (that'll change all the flags).
Does that mean you want this change for 19.03 directly? You should probably make this pr against 19.03 then, as my comment above won't be a problem. |
Postscript support used to work in 18.09; so I'd like to see this regression fixed soon and also for the 19.03 release. I could make one PR just for the postscript fix for master/19.03, and then make the other changes against the 3.32 branch (including meson migration if you want). @worldofpeace Does that work for you? |
Evince should work just fine even if you don't use nautilus. The flag just builds an extension for nautilus, which shows additional file properties. Are you concerned about the increase in closure size? I don't really need the extension, but it is an easy addition which is hard to build otherwise. |
Can we wait with this until GNOME 3.32 is merged? The expression was
massively rewritten.
Moreover, we do not actually want Evince to depend on Nautilus, we would
need to move the module to a separate output as Deja Dup does, I think. See #32817
…On Mon, 25 Mar 2019, 15:49 Gabriel Ebner, ***@***.***> wrote:
The postscript fix needs to be backported to the release branch as well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#58259 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AArCYzxFr7I2obmc3zuOvSY-Ihnh78_eks5vaOH5gaJpZM4cHEcv>
.
|
My actual problem with the extension can be seen at #32817. Though I think we should be fine to fix this just for 19.03 |
😄 Looks like we responded at the same time. |
Ok, I pushed just the postscript bugfix to 19.03 and master now. I'll make a new PR against gnome-3.32 that enables the other backends but keeps the nautilus extension disabled for now. |
Motivation for this change
I could no longer open postscript files in evince. While I was at it, I also enabled all other formats (DVI, XPS, PDF multimedia) as well as the nautilus extension. (The only features not enabled now are the browser plugin, the API docs, and the thumbnail cache.)
There is a slight increase in closure size (probably due to the gstreamer/nautilus dependency):
Many of these dependencies are probably already in the system closure (e.g. nautilus depends on gstreamer as well). We could add an
evinceLight
version that disables some/most features.cc @jtojnar @vcunat
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)