atril seems to require gvfs for metadata support, just like evince, but doesn't express it in any way. Might be good to look into that and depend on it with some IUSE=+metadata or unconditionally or at least elog/whatever something
Curious about a couple points: 1) Does this feature require a rebuild to enable, or is it handled by a dependency (libraries, pipes, or otherwise) at runtime which may or may not be fulfilled, removed, changed, etc. at a later date + properly detected when available. 2) best I can tell - nothing in the ebuilds for atril seems to mention metadata or gvfs (and it's not in the upstream docs either) nor does a quick glance at [ configure.ac ] seem to explicitly mention it. Is this feature provided by gio or does it come from somewhere else? (anyone with relevant knowledge could probably answer this) 3) It's possible that other users (I haven't personally, but also people other than myself) have never used evince, so saying "just like evince" as the only information about the feature you're describing is likely vague enough that more information will help track down this feature / behavior / bug for testing or modification of dependencies, etc. What's exactly is this evince-like metadata / gvfs feature?
(In reply to Mart Raudsepp from comment #0) > atril seems to require gvfs for metadata support, just like evince, but > doesn't express it in any way. Might be good to look into that and depend on > it with some IUSE=+metadata or unconditionally or at least elog/whatever > something Where do you see that Atril requires gvfs? As far as I can tell, all the metadata bits are using glib. Based on a lazy search of github's source https://github.com/mate-desktop/atril/search?q=gvfs&type=Code&utf8=%E2%9C%93, there are two fixmes suggesting using gvfs, but no other references to gvfs as far as a preliminary look revealed.
This was what other people ended up with for evince. So maybe that logic was wrong and GIO is able to save metadata without /usr/libexec/gvfsd-metadata backing it too (not sure and hard to test getting rid of gvfs on a GNOME system; maybe I can hide the metadata daemon from it...). I'll have to recheck the logic.. g_file_info_set_attribute_string docs say "Sets the attribute to contain the given attr_value, if possible". I thought it to not possible without gvfsd-metadata, but this information might be outdated or never fully correct. I believe if it turns out to not be possible, you just lose saving bookmarks and titles cache or something - what that in turn means for the user visibly - I'm not fully sure. The existing references are to set a key in gsettings I believe, to indicate if old metadata pre-gio has been migrated over to gio, but the key name contains "migrated-to-gvfs", not gio, suggesting gvfs is needed too. I'll look deeper later on to get this sorted properly for both atril and evince.
