Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: haiti-1.3.0
Date: Tue, 05 Jul 2022 04:52:46 +0200	[thread overview]
Message-ID: <20220705025246.Uhjn_N_bzxLjmvO1BpWUXr1DTBhQQdsKZylTQ9heod4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37804@inbox.vuxu.org>

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

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/pull/37804#issuecomment-1174546869

Comment:
> It's a bit harsh to assume that and say it like that

Sorry, but I only assume that because you wrote the tool and try to submit this tool to multiple distro.

> but ok, I guess security tools are not welcome on this distro.

Security tools are very welcomed in this distro. In facts, all tools which will be used by our users will be welcomed.
However, security tools should go under auditing before introduction. And tools should be introduced by users who will use THE tools ON Void Linux. I can see the former (as you wrote it) but not the former (noone specifically asked for it).

> But if you think too few users will use it, it's not necessary needed to include and build it by default.

I think NO Void Linux users will use it. Evident: noone ever asked for it, except you, who won't use Void Linux.

> I see there are [restricted repositories](https://docs.voidlinux.org/xbps/repositories/restricted.html) on Void so they are included in void-packages but need to be built manually by users.

Maintaining a software also costs. Build and distribute are easy, since machine are cheap. Human cost is not.

> Else I guess I'll have to submit it to non-official [VUR](https://github.com/vb-linux/VUR).

I only know VUR because of your comments.

> I'm new to Void and I'm discovering it, I took a lot of time to submit a PR and test it and reading the doc rather than opening a feature request issue. I was expecting a more welcoming answer even for a refusal.



  parent reply	other threads:[~2022-07-05  2:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02 17:30 [PR PATCH] add haiti and its dependencies noraj
2022-07-03  9:53 ` New package: haiti-1.3.0 sgn
2022-07-03 15:48 ` noraj
2022-07-03 18:11 ` noraj
2022-07-03 18:19 ` [PR PATCH] [Updated] " noraj
2022-07-03 22:55 ` sgn
2022-07-03 22:55 ` [PR PATCH] [Closed]: " sgn
2022-07-04 11:01 ` noraj
2022-07-05  2:52 ` sgn [this message]
2022-07-05  2:53 ` sgn
2022-07-05  2:53 ` sgn
2022-07-05  2:57 ` sgn
2022-07-05  7:51 ` noraj
2022-07-05 10:13 ` sgn
2022-07-05 10:27 ` noraj

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=20220705025246.Uhjn_N_bzxLjmvO1BpWUXr1DTBhQQdsKZylTQ9heod4@z \
    --to=sgn@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).