From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: Nextcloud
Date: Fri, 23 Dec 2022 17:55:56 +0100 [thread overview]
Message-ID: <20221223165556.O-NzZt1MBREMGlogRiA-e_tkbCME7NtWHVXaORWTgQ4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13850@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/13850#issuecomment-1364113854
Comment:
I do not think this is a good fit for void repositories.
* updates have to happen by one major version every time
* the user has to click on the update button in the UI before a new update comes otherwise they will have to downgrade, click on the button, update one version, click on the button again, etc.
* users can not click on the update button in the administration settings otherwise they will break the package's consistency and get downgraded with the next xbps nextcloud update
* it would be just a repackaging of 400MB of static files, there is nothing to build, so people can as well just extract the tarball to the right location by themselves
If you want to use nextcloud, either use docker or their installer script that also properly handles updates through multiple major versions.
next prev parent reply other threads:[~2022-12-23 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13850@inbox.vuxu.org>
2020-12-15 2:43 ` harrisonthorne
2022-12-23 16:55 ` paper42 [this message]
2022-12-23 20:20 ` [ISSUE] [CLOSED] " classabbyamp
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=20221223165556.O-NzZt1MBREMGlogRiA-e_tkbCME7NtWHVXaORWTgQ4@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).