From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New Package: vsv@1.3.2
Date: Wed, 08 Jan 2020 06:51:04 +0100 [thread overview]
Message-ID: <20200108055104.YyZYDtCJKpUcBQbiv2gEqznNVk4Qh3jJxqg0QhnRJU0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17979@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
There's a closed pull request on the void-packages repository
New Package: vsv@1.3.2
https://github.com/void-linux/void-packages/pull/17979
Description:
Summary
======
This adds [vsv](https://github.com/bahamas10/vsv) ([blog post intro](https://www.daveeddy.com/2018/09/20/vsv-void-service-manager/)). This a bash wrapper around `sv` to add some fanciness to managing runit.
Personal Testimony
----------------------------
I install `vsv` almost immediately on every void installation I make... I'd recommend giving it a quick try if you haven't for nothing more than to just get a quick summary with a simple command:
Possible Issues
---------------------
1. The name: I made it `vsv` to stand for `Void Service Manager`. This is short-sighted at best as this can work on more than just Void - basically any OS that has runit and `sv` installed. Also, this isn't an *official* Void sanctioned piece of software. I haven't included `Void` in the name in the template and instead just left it as `vsv`... but I could see this potentially being an issue.
2. `vsv` is already used in this repo as one of the built in commands. I don't think this is a huge issue since aliases and bash/sh functions will always be preferred over external commands, but just something to note.
3. This doesn't meet the quality requirements in the contributing handbook - this software is not compiled.
prev parent reply other threads:[~2020-01-08 5:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 2:28 [PR PATCH] " voidlinux-github
2020-01-08 5:51 ` voidlinux-github [this message]
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=20200108055104.YyZYDtCJKpUcBQbiv2gEqznNVk4Qh3jJxqg0QhnRJU0@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).