[Slackbuilds-users] new slacker Discord update

[Jeremy Hansen]

On Thu, Jul 10, 2025, 5:22 PM Joshua Lee <josh at 10leej.com> wrote:

> Hello I'm unfortunately new here to slackware. But I got it setup and
> running, and got discord installed. Well it seems that discord got an
> update which I managed to get installed perfectly fine.


I'm the maintainer for the discord package on SlackBuilds and keep it up to
date. The next update to 0.0.101 has already been done and is in my branch
waiting for the next public release (probably around 24ish hours from now,
depending on when Willy or one of the other admins get to it).

Public releases are only done typically once per week, so even if I make
the update immediately, users will need to wait until the next SBo public
update is done.

Alternatively, you can use the information in the bottom of the README to
bypass the update warning until the next update is pushed.

But how would I go petitioning the slackbuild maintainer to update the
> package?
>

You'd typically notify them via email. However, it's also a good idea to
see how active they are and how recently it was last updated so you're not
bombarding them with updates they're likely already aware of. Discord
updates so frequently that I usually have one pushed each week for SBo's
public update.

You can check the changelog on SBo to see how frequently the maintainer is
updating it. As you can see in the link below, I rarely miss an update
(generally only if I'm out of town for the entire week).

https://git.slackbuilds.org/slackbuilds/log/network/discord?h=15.0


Do i post it as a new submission?
>

You shouldn't do this without the maintainer's permission or permission
from the admins if the maintainer has disappeared. You can email the
maintainer a diff to make it easier for them to update.

Jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250710/03a7a95e/attachment-0001.htm>