From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: bzip2-devel: add pkgconfig file
Date: Mon, 29 May 2023 10:36:04 +0200 [thread overview]
Message-ID: <20230529083604.MGNK2YBISUSxxz4PepYSyODh15H7XxF7QjNK2hGxspw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40468@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]
There's a merged pull request on the void-packages repository
bzip2-devel: add pkgconfig file
https://github.com/void-linux/void-packages/pull/40468
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
Adapted from [Arch Linux](https://github.com/archlinux/svntogit-packages/commit/e2cc08098f31fc7110131782626d22939731b7d5)
Context: upstream has been unresponsive about requests for pkgconfig files in the past, but Arch and Alpine include their own, at least.
Also, the experimental future development project added the file back in 2019: https://gitlab.com/bzip2/bzip2/-/commit/70ec984159c8263fdd4aac7c4670977aff0fe5b3
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2023-05-29 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 13:22 [PR PATCH] " tranzystorek-io
2022-11-15 11:41 ` 0x5c
2022-11-15 11:42 ` 0x5c
2023-02-14 2:02 ` github-actions
2023-02-26 19:43 ` [PR PATCH] [Updated] " tranzystorek-io
2023-05-29 1:57 ` github-actions
2023-05-29 8:36 ` the-maldridge [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=20230529083604.MGNK2YBISUSxxz4PepYSyODh15H7XxF7QjNK2hGxspw@z \
--to=the-maldridge@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).