public inbox for bzip2-devel@sourceware.org
 help / color / mirror / Atom feed
From: "eschwartz93 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: bzip2-devel@sourceware.org
Subject: [Bug bzip2/31660] Add bzip2.pc pkg-config file
Date: Sun, 21 Apr 2024 01:46:12 +0000	[thread overview]
Message-ID: <bug-31660-11876-yz7lDJUBDI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31660-11876@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31660

--- Comment #2 from Eli Schwartz <eschwartz93 at gmail dot com> ---
(In reply to Ryan Carsten Schmidt from comment #0)
> Please add a pkg-config bzip2.pc file.
> 
> Code to do so was committed in 2019:
> 
> https://gitlab.com/bzip2/bzip2/-/commit/
> 70ec984159c8263fdd4aac7c4670977aff0fe5b3
> 
> yet there does not appear to be a release of bzip2 containing
> this improvement.


That repository is an unofficial fork which, if I understand correctly, has
goals that are in conflict with the original project...

Note that the patch I submitted here depends on autoconf since the .pc file
must contain the --prefix, --includedir, --libdir (and therefore has to be a
built file).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-04-21  1:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 20:29 [Bug bzip2/31660] New: " sourceware at ryandesign dot com
2024-04-19 20:36 ` [Bug bzip2/31660] " sourceware at ryandesign dot com
2024-04-20  7:44 ` sam at gentoo dot org
2024-04-21  1:46 ` eschwartz93 at gmail dot com [this message]
2024-04-21  2:33 ` sourceware at ryandesign dot com

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=bug-31660-11876-yz7lDJUBDI@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=bzip2-devel@sourceware.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).