FS#42461 - [gnome-online-accounts] Make gvfs-goa (optional) dependency

Attached to Project: Arch Linux
Opened by Karol Babioch (johnpatcher) - Monday, 20 October 2014, 14:45 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 14 October 2017, 15:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

gnome-online-accounts relies on gvfs-goa for file integration with nautilus. This wasn't obvious to me and it took me a while to figure this one out. I would prefer for gvfs-goa to be an dependency of gnome-online-accounts, at least an optional one, which would make it more obvious for lazy people ;).
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 14 October 2017, 15:18 GMT
Reason for closing:  Implemented
Additional comments about closing:  gnome-online-accounts 3.18.0-3
Comment by mattia (nTia89) - Wednesday, 19 November 2014, 20:25 GMT
where does gnome-online-account uses nautilus or viceversa?
Comment by Ross Lagerwall (rosslagerwall) - Wednesday, 01 April 2015, 22:41 GMT
I think it's for integration with accessing files on owncloud accounts .
Comment by Hussam Al-Tayeb (hussam) - Monday, 12 October 2015, 10:27 GMT
gvfs-goa only depends on gvfs main package and gnome-online-accounts so no additional dependencies.
What difference does it make to you if its files are on your computer or not?

/usr/lib/gvfs/gvfs-goa-volume-monitor only runs if you are mounting a 'cloud' storage account, otherwise it is just sitting there on your computer and not using system resources.
Comment by Karol Babioch (johnpatcher) - Tuesday, 13 October 2015, 13:48 GMT
If we wouldn't care what files end up being on our systems, we would choose other distributions. One reason for choosing Arch is to keep your installation clean and small. In this case, however, I was complaining about the fact that one package relies on the other one without any (optional) dependency.
Comment by Hussam Al-Tayeb (hussam) - Tuesday, 13 October 2015, 14:19 GMT
Simple and clean normally implies staying close to upstream (vanilla) and not the opposite including when a piece of software was written with the assumption that a runtime dependency is going to be available.
You can always edit the desc file for gnome-online-accounts and remove the gvfs-goa dependency and uninstall it. This avoids cases where a new user may install gnome-online-accounts, find a non-working portion of the software and assuming something is broken just to find out later that it was deemed optional with no static criteria.
(Please note that the above is not an opinion, but rather an interpretation of Linux software management).
As for my actual opinion, I don't even mind dependencies being completely removed. There, however, needs to be a static criteria as to what is deemed optional or necessary. There is none right now which creates lack of consistency.

Pacman is very versatile in this area. It is mostly why people have stayed at ArchLinux for a decade or more with the spirit that distributions should not be compared or put in competitive situations.

Loading...