--- Begin Message ---
|
Subject: |
remove Google support from GVFS? |
|
Date: |
Wed, 24 Nov 2021 06:00:15 +0100 |
I'd love to say it's because I want the package to be more in line with
libre software guidelines, but honestly I just don't want WebKitGTK as
a transitive input. A few weeks ago I had to remove GVFS from my system
because WebKitGTK was failing to build.
Then again if I had to connect to Google Drive or Picasa or whatever
I'd rather do it through libre software, so maybe it should stay.
Too bad we still don't have package options.
So, what do yall think, should I just create a custom package on my own
channel that disables all that junk, or is this something everyone
wants?
ps.: if any GVFS devs are reading this, the bug that caused me to
almost delete my entire file system is still unaddressed. :)
https://gitlab.gnome.org/GNOME/gvfs/-/issues/202
https://gitlab.gnome.org/GNOME/gvfs/-/issues/364
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#52073: remove Google support from GVFS? |
|
Date: |
Fri, 31 Dec 2021 13:13:35 -0500 |
On Fri, Dec 31, 2021 at 01:24:55PM +0100, Liliana Marie Prikler wrote:
> Given that we have GNOME 40/41 on master right now with GVFS supporting
> Google as it did before, is this still relevant?
Since the bug report was a reaction to WebKitGTK being broken, and it's
no longer broken, I'm closing the ticket [0].
When packages break occasionally, we have to decide if we should remove
them from the distro or if we can should try maintain the status quo.
My experience with WebKitGTK is that the build is quite reliable. That's
why I pushed the broken update to begin with: it always worked in the
past. There's no need to rewrite the dependency graph just because I was
lazy and don't have a very fast computer.
[0] Anyone can reopen it by sending a message with "reopen 52073" to
<control@debbugs.gnu.org>.
https://debbugs.gnu.org/server-control.html
--- End Message ---