FS#55625 - Nextcloud: Add an update alpm-hook to force occ upgrade

Attached to Project: Community Packages
Opened by Bas Bleeker (Bubbel) - Wednesday, 13 September 2017, 20:03 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 14 September 2017, 09:44 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
As describes in the forum: https://bbs.archlinux.org/viewtopic.php?id=229941
When nextcloud, or a nextcloud app updates, it often needs an upgrade routine.
Add this as a post-install hook into pacman and you're done!

Additional info:
* For all versions of Nextcloud
* Place the attached file in /etc/pacman.d/hooks/

The file calls 'occ' from the nextcloud install and issues an upgrade command, but only when a package called nextcloud, or nextcloud-app-* is installed or upgraded.

Seems like a good candidate for the nextcloud package, I think.
   nextcloud.hook (0.3 KiB)
This task depends upon

Closed by  Sergej Pupykin (sergej)
Thursday, 14 September 2017, 09:44 GMT
Reason for closing:  Fixed
Additional comments about closing:  in svn/trunk only, attached hook used.
Comment by Eli Schwartz (eschwartz) - Thursday, 14 September 2017, 00:45 GMT
Often, file triggers are better. You could trigger the hook on changes to usr/share/webapps/nextcloud/apps/*/ which would work independent of the naming scheme for the package, I think.
Comment by Bas Bleeker (Bubbel) - Thursday, 14 September 2017, 06:46 GMT
True, file triggers are possible. It's a question of aesthetics, I think. I would stay with the package names. But that's just my idea.

Loading...