public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michal Schorm <mschorm@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/nemo] rawhide: Downgrade 'Requires: gvfs-goa' to 'Recommends'
Date: Sun, 26 Jul 2026 20:57:58 GMT	[thread overview]
Message-ID: <178509947823.1.9927884657565046896.rpms-nemo-4d9b0e3f7889@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/nemo
            Branch : rawhide
            Commit : 4d9b0e3f7889ba832266a673e6409c544d8a211a
            Author : Michal Schorm <mschorm@redhat.com>
            Date   : 2026-07-26T19:56:04+02:00
            Stats  : +1/-1 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/nemo/c/4d9b0e3f7889ba832266a673e6409c544d8a211a?branch=rawhide

            Log:
            Downgrade 'Requires: gvfs-goa' to 'Recommends'

GNOME Online Accounts integration is an optional feature — nemo
works fully without it. Users who do not configure Google Drive,
OneDrive, or other GOA-backed storage have no use for the gvfs-goa
backend.

'gvfs-fuse' (still a hard Requires) provides the core FUSE-based
filesystem support. The GOA backend is a supplementary data source
that should be recommended but not required.

This reduces the dependency footprint for minimal Cinnamon
installations that do not use cloud storage integration.

Co-Authored-By: Claude AI <noreply@anthropic.com>

---
diff --git a/nemo.spec b/nemo.spec
index d94a6a8..7883abf 100644
--- a/nemo.spec
+++ b/nemo.spec
@@ -13,7 +13,7 @@ ExcludeArch:   %{ix86}
 
 Requires:       redhat-menus
 Requires:       gvfs-fuse%{?_isa}
-Requires:       gvfs-goa%{?_isa}
+Recommends:     gvfs-goa%{?_isa}
 Requires:       xapps%{?_isa} >= 2.2.0
 # required by nemo-action-layout-editor
 Requires:       libxmlb%{?_isa}

                 reply	other threads:[~2026-07-26 20:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178509947823.1.9927884657565046896.rpms-nemo-4d9b0e3f7889@fedoraproject.org \
    --to=mschorm@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox