From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: corosync-3.0.2
Date: Thu, 05 Sep 2019 12:28:23 +0200 [thread overview]
Message-ID: <20190905102823.7ErxyY2twauDmUks50USjDmwH_irHtkl1HMsa5T42H8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14061@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
New comment by jirib on void-packages repository
https://github.com/void-linux/void-packages/pull/14061#issuecomment-528302061
Comment:
> > => looks odd, I think it should be >=. However you should not need to add that manually since dependencies on shard libraries are automatically detected by xbps-src while building the package. Following the usual pattern for libraries, the sub-package should be called `libcorosync'. Haven't reviewed the rest of the template yet.
>
> Thanks, it was this typo.
>
> BTW, as libknet1 does not build on musl archs, how should this package be treated? Should I define it to be only for non-musl archs? IIUC corosync can't be easily told to be build without 'knet' transport now, see [corosync/corosync#501](https://github.com/corosync/corosync/issues/501)
Solved, I'm preparing libknet1/libnozzle1 (new pkg) fix which would support musl, https://github.com/void-linux/void-packages/pull/14215
next prev parent reply other threads:[~2019-09-05 10:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14061@inbox.vuxu.org>
2019-09-01 21:13 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-01 21:24 ` voidlinux-github
2019-09-01 21:24 ` voidlinux-github
2019-09-01 21:54 ` voidlinux-github
2019-09-01 21:55 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-01 21:55 ` voidlinux-github
2019-09-05 10:28 ` voidlinux-github [this message]
2019-09-05 10:28 ` voidlinux-github
2019-09-05 11:22 ` [PR PATCH] [Closed]: " 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=20190905102823.7ErxyY2twauDmUks50USjDmwH_irHtkl1HMsa5T42H8@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).