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 12:13:46 +0200	[thread overview]
Message-ID: <20220705101346.byldIicoXlK9uu4__P3QslV6qRUAOB3RHHZxE8XK1bo@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: 2996 bytes --]

New comment by sgn on void-packages repository

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

Comment:
> > Sorry, but I only assume that because you wrote the tool and try to submit this tool to multiple distro.
> 
> The tool is from 2019 and have already spread.

In `haiti` repository, I only see BlackArch, and FreeBSD ports, also AUR (which, I think, everyone can submit) and Gentoo overlay.
So, I'm not sure how you define "spread".
This isn't a confrontation. It's just my observation.

> I'm not actually trying to ship it in more distro for fame or whatever but because I had feedback from users that they don't want to `gem install` on their distro so providing them a distro package is easier and more maintainable for them. That's all.

Citation requested, please.

> 
> > 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 latter (noone specifically asked for it).
> 
> That make sense.
> 
> > I think NO Void Linux users will use it. Evident: noone ever asked for it while `haiti` was release a stable release for more than 1 year, except you, who won't use Void Linux.
> 
> I know a least one Void user which use it but he is using the docker image or the distro package in an ArchLinux package because there is no Void package. Maybe there are more that are actually using a workaround and don't feel the need to request for it but would switch to void package if available.

Citation requested, again.

> But again it make sens to me to not include it if it targets too few users. 

No, it's fine to be used by a few users, (you're not using Void Linux, so I don't think you're counted).

> On ArchLinux there is an user repository (AUR) where people can vote for package, so eventually a dev can provide it's tool on the AUR and if it's a massive success and lot of people vote for it sometimes ArchLinux dev offers to include the tool in the official repo. Unfortunately there is no such a mechanism for Void.

Users can request to package it. See https://github.com/void-linux/void-packages/issues?q=is%3Aissue+is%3Aopen+label%3Arequest for current requests.

> 
> > Maintaining a software also costs. Build and distribute are easy, since machine are cheap. Human cost is not.
> 
> For that I can maintain the Void package and bump / test it at each Haiti release, I put orphan because I thought it required the name of an official team member.

Maintaining a distro isn't simply bump version of a package, but also integrate with other parts of system.

> 
> > I only know VUR because of your comments.
> 
> Yay, it seems very little know. Maybe you know another more popular void user repository alternative?

No, I don't



  parent reply	other threads:[~2022-07-05 10:13 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
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 [this message]
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=20220705101346.byldIicoXlK9uu4__P3QslV6qRUAOB3RHHZxE8XK1bo@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).