Github messages for voidlinux
 help / color / mirror / Atom feed
From: bobertlo <bobertlo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Request: Discord
Date: Fri, 20 Mar 2020 18:04:53 +0100	[thread overview]
Message-ID: <20200320170453.lsVThnlrt2UhrRmX_wXrIPvfTj186pgpx6-uvslKSy8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20107@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 848 bytes --]

New comment by bobertlo on void-packages repository

https://github.com/void-linux/void-packages/issues/20107#issuecomment-601809332

Comment:
@Frick-David I originally was going to post a more detailed overview, but we really do not want to duplicate the `xbps-src` documentation in the *void-packages* repo. I think more valuable would be a more clear and simple quick start in the *void-packages* repo readme. Not that the existing documentation is *bad*, but this comes up *a lot*.

Edit: also see the `xbps-mini-builder` referenced in the docs if you really want to keep automated restricted package building. From personal experience it is probably simpler to just update manually in cases like this. Discord in particular does not need package updates very often at all. Like once or twice a year in my experience, and it will tell you :)

  parent reply	other threads:[~2020-03-20 17:04 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16  1:57 [ISSUE] " Frick-David
2020-03-16  2:01 ` abenson
2020-03-16  2:06 ` abenson
2020-03-16  2:26 ` bobertlo
2020-03-16  7:57 ` Frick-David
2020-03-16  8:24 ` kyunal
2020-03-16 10:21 ` Duncaen
2020-03-16 10:25 ` kyunal
2020-03-16 10:27 ` Duncaen
2020-03-16 10:28 ` Duncaen
2020-03-16 18:37 ` Arzte
2020-03-16 18:38 ` Arzte
2020-03-16 18:40 ` Arzte
2020-03-16 18:41 ` Arzte
2020-03-16 18:44 ` Arzte
2020-03-16 18:50 ` Arzte
2020-03-16 18:50 ` Arzte
2020-03-16 20:07 ` kyunal
2020-03-16 20:22 ` Duncaen
2020-03-16 20:25 ` kyunal
2020-03-17 20:00 ` Frick-David
2020-03-20  5:32 ` Frick-David
2020-03-20  6:01 ` Frick-David
2020-03-20  6:04 ` Frick-David
2020-03-20  6:04 ` Frick-David
2020-03-20 16:15 ` wundrweapon
2020-03-20 16:16 ` wundrweapon
2020-03-20 17:02 ` bobertlo
2020-03-20 17:04 ` bobertlo [this message]
2020-03-20 21:04 ` Arzte
2020-03-20 21:23 ` Duncaen
2020-03-20 21:24 ` Duncaen
2020-03-20 21:24 ` Duncaen
2020-03-23 13:42 ` Frick-David
2020-04-18 13:51 ` rc-05
2021-01-08 22:24 ` kawaiiamber
2021-01-08 22:30 ` Duncaen
2022-04-16  2:02 ` github-actions
2022-04-30  2:13 ` [ISSUE] [CLOSED] " github-actions

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=20200320170453.lsVThnlrt2UhrRmX_wXrIPvfTj186pgpx6-uvslKSy8@z \
    --to=bobertlo@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).