Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: vsv: update to 2.0.0
Date: Tue, 07 Feb 2023 18:09:18 +0100	[thread overview]
Message-ID: <20230207170918.ZiB-_XlzV7U8APyK67Ef2DRnXdHC0RVxIVXykohhkos@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42099@inbox.vuxu.org>

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

There's a merged pull request on the void-packages repository

vsv: update to 2.0.0
https://github.com/void-linux/void-packages/pull/42099

Description:
`vsv` was rewritten from Bash to Rust so this template reflects that change - the user-facing CLI interface has not changed.

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-2.36)
- I built this PR locally for these architectures:
  - armv6l (cross)

---

I built the package locally:

```
./xbps-src pkg vsv # exited successfully
./xbps-src -a armv6l pkg vsv # exited succkssefully
```

I tested to make sure the package looked sane (had the files i expected):

```
$ xbps-query --repository=hostdir/binpkgs -f vsv
/usr/bin/vsv
/usr/share/licenses/vsv/LICENSE
/usr/share/man/man8/vsv.8
```

I installed the package on my system to make sure 1. it ran 2. was a compiled binary and not a bash script.

```
$ sudo xbps-install --repository hostdir/binpkgs vsv
$ file /usr/bin/vsv
/usr/bin/vsv: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=351cfbeb98cf65b1d3c34e7296348b96384521d2, for GNU/Linux 3.2.0, stripped
$ vsv -V
vsv 2.0.0
```

      parent reply	other threads:[~2023-02-07 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05 19:27 [PR PATCH] vsv: update to v2.0.0 bahamas10
2023-02-07  8:14 ` classabbyamp
2023-02-07 17:03 ` [PR PATCH] [Updated] vsv: update to 2.0.0 bahamas10
2023-02-07 17:04 ` bahamas10
2023-02-07 17:09 ` classabbyamp [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=20230207170918.ZiB-_XlzV7U8APyK67Ef2DRnXdHC0RVxIVXykohhkos@z \
    --to=classabbyamp@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).