From: bingulo <bingulo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: civetweb-1.15
Date: Tue, 02 Aug 2022 20:01:38 +0200 [thread overview]
Message-ID: <20220802180138.zShQnpF_u4Rv19ICw3iH6z84MbjRdNxfCrs88HLfS-8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38419@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
New comment by bingulo on void-packages repository
https://github.com/void-linux/void-packages/pull/38419#issuecomment-1203047691
Comment:
> yes, and I think there should be a `libcivetweb` subpackage too
>
> ```shell
> libcivetweb_package() {
> short_desc+=" - library"
> pkg_install() {
> vmove usr/lib/*.so.*
> }
> }
> ```
Should I add this subpackage as dependency for main package? I tested and didn't find any issue without it.
next prev parent reply other threads:[~2022-08-02 18:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 3:27 [PR PATCH] " bingulo
2022-08-02 3:41 ` [PR REVIEW] " classabbyamp
2022-08-02 3:41 ` classabbyamp
2022-08-02 3:41 ` classabbyamp
2022-08-02 3:41 ` classabbyamp
2022-08-02 16:46 ` [PR PATCH] [Updated] " bingulo
2022-08-02 16:46 ` bingulo
2022-08-02 16:47 ` bingulo
2022-08-02 16:47 ` [PR REVIEW] " bingulo
2022-08-02 16:54 ` [PR PATCH] [Updated] " bingulo
2022-08-02 16:55 ` [PR REVIEW] " classabbyamp
2022-08-02 16:58 ` [PR PATCH] [Updated] " bingulo
2022-08-02 17:02 ` classabbyamp
2022-08-02 17:07 ` bingulo
2022-08-02 17:13 ` classabbyamp
2022-08-02 17:36 ` [PR PATCH] [Updated] " bingulo
2022-08-02 17:40 ` bingulo
2022-08-02 18:01 ` bingulo [this message]
2022-08-02 18:04 ` classabbyamp
2022-08-02 18:08 ` [PR PATCH] [Updated] " bingulo
2022-08-02 18:10 ` classabbyamp
2022-08-02 18:13 ` [PR PATCH] [Updated] " bingulo
2022-08-02 18:15 ` classabbyamp
2022-08-02 18:19 ` bingulo
2022-08-02 18:21 ` classabbyamp
2022-08-02 18:23 ` [PR PATCH] [Updated] " bingulo
2022-08-02 20:07 ` bingulo
2022-08-02 20:08 ` classabbyamp
2022-08-02 20:09 ` [PR PATCH] [Updated] " bingulo
2022-08-02 20:13 ` classabbyamp
2022-08-02 20:14 ` bingulo
2022-08-02 20:16 ` [PR PATCH] [Updated] " bingulo
2022-08-02 20:21 ` bingulo
2022-08-02 20:23 ` bingulo
2022-08-03 15:30 ` paper42
2022-08-03 16:39 ` [PR PATCH] [Updated] " bingulo
2022-08-03 16:40 ` bingulo
2022-08-03 16:42 ` bingulo
2022-08-07 2:28 ` [PR PATCH] [Updated] " bingulo
2022-08-08 17:34 ` bingulo
2022-08-08 17:34 ` [PR PATCH] [Closed]: " bingulo
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=20220802180138.zShQnpF_u4Rv19ICw3iH6z84MbjRdNxfCrs88HLfS-8@z \
--to=bingulo@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).