You are not logged in.

#1 2026-01-14 12:45:41

smileyzn
Member
Registered: 2026-01-14
Posts: 2

Papers vs Evince package dependency in new GNOME setup

Hi folks.

Some packages needs a evince package as dependency.

Required By (14)

    phosh
    phosh (testing)
    sugar-activity-browse
    sugar-activity-read
    sushi
    geeqie (optional)
    gtk3 (optional)
    gtk4 (optional)
    lib32-gtk3 (optional)
    rosegarden (optional)
    texstudio (optional)
    xdg-desktop-portal-gnome (optional)
    xdg-desktop-portal-gtk (optional)
    geeqie (make)

But for now, papers is the core application of GNOME.
Is possible to replace evince with papers?

I always try to use GNOME core apps, for now arch needs evince, if i install papers then i get duplicated PDF reader app.

Thanks for help

Offline

#2 2026-01-14 13:08:50

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,944

Re: Papers vs Evince package dependency in new GNOME setup

The creators of those apps decide what they need to depend on , not archlinux .

Only 4 applications on archlinux have a hard dependency on evince .

$ pactree --sync --reverse evince
evince
├─phosh
│ └─phosh-mobile-settings
├─sugar-activity-browse
├─sugar-activity-read
└─sushi
$ 

You can try to convince their devs to switch to gnome papers or look for alternatives that don't need evince.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 2026-01-14 13:20:07

smileyzn
Member
Registered: 2026-01-14
Posts: 2

Re: Papers vs Evince package dependency in new GNOME setup

Thanks for tip, i just try to do that.

To be honest, i found that only package that was installed that uses evince in default GNOME install is sushi.

Offline

#4 2026-01-14 15:45:52

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,723

Re: Papers vs Evince package dependency in new GNOME setup

You completely misinterpreted what Lone_Wolf told you. The actual software devs are the ones that need to switch, not the Arch packager; filing an issue on Arch's gitlab does nothing.

Offline

Board footer

Powered by FluxBB