From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: dino-0.1.0
Date: Tue, 04 Feb 2020 04:03:37 +0100 [thread overview]
Message-ID: <20200204030337.9cCbiN-_Ll1yp7lwHbeI6-eQ4WTdsdHENINSW6eQkJQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18648@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
New comment by anjandev on void-packages repository
https://github.com/void-linux/void-packages/pull/18648#issuecomment-581720281
Comment:
@toogley thank you for the example build script. The current commit in this PR compiles dino to completion without plugins. I referenced your build script and `libcanberra-devel` was added but might not be needed - I need to do some testing on whether this dependency is needed.
Enabling the omemo plugin causes a linking error. Getting dino to compile without plugins is a good stepping stone but as @v0idifier has stated, dino was created to make encrypted communication easy and the default. I need fix omemo before this package can be merged with void repos. Any suggestions or help is much appreciated!
next prev parent reply other threads:[~2020-02-04 3:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 2:34 [PR PATCH] " voidlinux-github
2020-01-30 3:11 ` [PR PATCH] [Updated] [WIP] " voidlinux-github
2020-01-30 3:18 ` voidlinux-github
2020-01-30 3:49 ` voidlinux-github
2020-01-30 5:39 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-30 5:46 ` voidlinux-github
2020-01-30 5:50 ` voidlinux-github
2020-01-30 6:59 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-30 7:01 ` voidlinux-github
2020-01-30 7:03 ` voidlinux-github
2020-01-30 21:31 ` voidlinux-github
2020-01-31 4:13 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-31 15:32 ` voidlinux-github
2020-02-01 2:58 ` voidlinux-github
2020-02-01 22:38 ` voidlinux-github
2020-02-01 22:40 ` voidlinux-github
2020-02-01 22:53 ` voidlinux-github
2020-02-03 10:05 ` voidlinux-github
2020-02-03 16:49 ` voidlinux-github
2020-02-04 0:44 ` voidlinux-github
2020-02-04 2:20 ` [PR PATCH] [Updated] " voidlinux-github
2020-02-04 2:29 ` voidlinux-github
2020-02-04 2:55 ` voidlinux-github
2020-02-04 3:03 ` voidlinux-github [this message]
2020-02-04 10:19 ` voidlinux-github
2020-02-04 10:20 ` voidlinux-github
2020-02-04 10:22 ` voidlinux-github
2020-02-04 10:24 ` voidlinux-github
2020-02-04 10:25 ` voidlinux-github
2020-02-04 20:42 ` voidlinux-github
2020-02-05 21:09 ` voidlinux-github
2020-02-06 5:44 ` voidlinux-github
2020-02-06 5:44 ` [PR PATCH] [Closed]: " voidlinux-github
2020-02-06 5:44 ` voidlinux-github
2020-02-06 9:06 ` voidlinux-github
2020-02-06 9:08 ` voidlinux-github
2020-02-06 9:37 ` voidlinux-github
2020-02-06 9:49 ` voidlinux-github
2020-02-06 19:33 ` voidlinux-github
2020-02-07 22:21 ` voidlinux-github
2020-02-07 22:32 ` voidlinux-github
2020-02-07 22:33 ` [PR PATCH] [Merged]: " voidlinux-github
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=20200204030337.9cCbiN-_Ll1yp7lwHbeI6-eQ4WTdsdHENINSW6eQkJQ@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).