From: Sam James <sam@gentoo.org>
To: Sam James via Bzip2-devel <bzip2-devel@sourceware.org>
Cc: Mark Wielaard <mark@klomp.org>,
Eli Schwartz <eschwartz93@gmail.com>,
soap@gentoo.org
Subject: Re: [PATCH bzip2 6/6] install a pkg-config file with instructions for linking to libbz2
Date: Thu, 13 Nov 2025 04:48:51 +0000 [thread overview]
Message-ID: <87zf8qa66k.fsf@gentoo.org> (raw)
In-Reply-To: <87tszx2psl.fsf@gentoo.org>
Sam James via Bzip2-devel <bzip2-devel@sourceware.org> writes:
> Sam James via Bzip2-devel <bzip2-devel@sourceware.org> writes:
>
>> Sam James via Bzip2-devel <bzip2-devel@sourceware.org> writes:
>>
>>> Eli Schwartz via Bzip2-devel <bzip2-devel@sourceware.org> writes:
>>>
>>>> On 11/10/24 6:59 PM, Eli Schwartz wrote:
>>>>> On 11/10/24 6:55 PM, Mark Wielaard wrote:
>>>>>> Hi,
>>>>>>
>>>>>> On Thu, Nov 07, 2024 at 12:15:52PM +0000, Sam James via Bzip2-devel wrote:
>>>>>>> Ping. These patches look good and I've tried them out locally too.
>>>>>>>
>>>>>>> We'd really love to clean up our packaging of bzip2 as it's a mess right
>>>>>>> now for different targets.
>>>>>>
>>>>>> Yeah, this has been pending way too long.
>>>>>>
>>>>>> I created a "pull request" on the new forge as a test:
>>>>>> https://forge.sourceware.org/bzip2/bzip2-fork/pulls/1
>>>>>
>>>>>
>>>>> Thanks, very exciting news! :)
>>>>
>>>>
>>>> Hey, any new updates? :)
>>>
>>> Ping -- we had to mock another bzip2 pkgconfig file today in a package
>>> (as we don't want to install our own in the bzip2 package unless/until
>>> it is upstream)
>>
>> Ping.
>
> ping
ping
next prev parent reply other threads:[~2025-11-13 4:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 3:45 [PATCH bzip2 1/6] install relative symlinks ~eschwartz
2022-06-03 4:20 ` [PATCH bzip2 2/6] port the build configuration to autoconf ~eschwartz
2022-06-09 5:56 ` Eli Schwartz
2022-06-03 4:48 ` [PATCH bzip2 4/6] make a couple program aliases symlinks instead of copies ~eschwartz
2022-06-03 4:54 ` [PATCH bzip2 5/6] install man page symlinks for a couple more symlinked commands ~eschwartz
2022-06-03 5:09 ` [PATCH bzip2 6/6] install a pkg-config file with instructions for linking to libbz2 ~eschwartz
2022-06-09 5:52 ` Eli Schwartz
2022-10-23 16:03 ` Sam James
2024-11-07 12:15 ` Sam James
2024-11-10 23:55 ` Mark Wielaard
2024-11-10 23:59 ` Eli Schwartz
2024-12-16 15:43 ` Eli Schwartz
2025-01-11 13:01 ` Sam James
2025-09-29 21:31 ` Sam James
2025-10-17 21:15 ` Sam James
2025-11-13 4:48 ` Sam James [this message]
2024-11-11 1:52 ` [PATCH] shared makefile: also respect LDFLAGS Eli Schwartz
2022-06-09 4:50 ` [PATCH bzip2 3/6] shared Makefile: add install rule ~eschwartz
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=87zf8qa66k.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=bzip2-devel@sourceware.org \
--cc=eschwartz93@gmail.com \
--cc=mark@klomp.org \
--cc=soap@gentoo.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 read-only IMAP folder(s) and NNTP newsgroup(s).