Github messages for voidlinux
 help / color / mirror / Atom feed
From: Logarithmus <Logarithmus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] common/shlibs: add shlibs for simavr
Date: Mon, 19 Oct 2020 17:25:42 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25741@inbox.vuxu.org> (raw)

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

There is a new pull request by Logarithmus against master on the void-packages repository

https://github.com/Logarithmus/void-packages common-shlibs-simavr
https://github.com/void-linux/void-packages/pull/25741

common/shlibs: add shlibs for simavr
Add missing shlib entries for `simavr`

A patch file from https://github.com/void-linux/void-packages/pull/25741.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-common-shlibs-simavr-25741.patch --]
[-- Type: text/x-diff, Size: 627 bytes --]

From a7a0180aeffcdeb9853f85b28fb0434774fc7316 Mon Sep 17 00:00:00 2001
From: Artur Sinila <opensource@logarithmus.dev>
Date: Mon, 19 Oct 2020 18:10:14 +0300
Subject: [PATCH] common/shlibs: add shlibs for simavr

---
 common/shlibs | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/common/shlibs b/common/shlibs
index 35f08f5f099..2a8981219d2 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -3991,3 +3991,5 @@ libneatvnc.so.0 neatvnc-0.2.0_1
 libtdjson.so.1.6.0 libtd-1.6.0_1
 libJudy.so.1 judy-1.0.5_1
 libsignal-protocol-c.so.2 libsignal-protocol-c-2.3.3_2
+libsimavr.so.1 simavr-1.6_2
+libsimavrparts.so.1 simavr-1.6_2

             reply	other threads:[~2020-10-19 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 15:25 Logarithmus [this message]
2020-10-19 15:39 ` sgn
2020-10-19 15:55 ` Duncaen
2020-10-19 15:57 ` Duncaen
2020-10-20  0:32 ` ahesford
2020-10-20  0:32 ` [PR PATCH] [Closed]: " ahesford

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25741@inbox.vuxu.org \
    --to=logarithmus@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).