Github messages for voidlinux
 help / color / mirror / Atom feed
From: ketlrznt <ketlrznt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: v2raya-bin-1.5.8.1_1.x86_64
Date: Tue, 02 Aug 2022 07:03:45 +0200	[thread overview]
Message-ID: <20220802050345.6j-oOanKDn1-GXJ4PNbcV0kzh49H6TYVVYcstheWma0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38420@inbox.vuxu.org>

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

New comment by ketlrznt on void-packages repository

https://github.com/void-linux/void-packages/pull/38420#issuecomment-1202019245

Comment:
> On void, users don't need to build packages from templates/sources themselves, that's what the builders do. Users would only be downloading the resulting binary package.

OK. I get your point. I will try to build it from scratch later.

Another problem is I think shipping such software in Void repository may cause legal affairs in some countries (which has Void Linux mirror), though its license allows redistributions. it would be better to make it "restricted" and don't distribute it, that's another reason why I choose to use binary file, as user could get the output only from template file.

  parent reply	other threads:[~2022-08-02  5:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02  4:31 [PR PATCH] " ketlrznt
2022-08-02  4:38 ` classabbyamp
2022-08-02  4:47 ` ketlrznt
2022-08-02  4:48 ` ketlrznt
2022-08-02  4:48 ` ketlrznt
2022-08-02  4:54 ` ketlrznt
2022-08-02  4:55 ` classabbyamp
2022-08-02  5:01 ` ketlrznt
2022-08-02  5:03 ` ketlrznt
2022-08-02  5:03 ` ketlrznt [this message]
2022-08-02  5:03 ` classabbyamp
2022-08-02  5:09 ` ketlrznt
2022-08-02  5:14 ` ketlrznt
2022-08-02  5:15 ` ketlrznt
2022-08-02  5:15 ` [PR PATCH] [Closed]: " ketlrznt

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=20220802050345.6j-oOanKDn1-GXJ4PNbcV0kzh49H6TYVVYcstheWma0@z \
    --to=ketlrznt@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).