public inbox for bzip2-devel@sourceware.org
 help / color / mirror / Atom feed
From: "sourceware at ryandesign 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 02:33:49 +0000	[thread overview]
Message-ID: <bug-31660-11876-ucLb4nIQus@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 #3 from Ryan Carsten Schmidt <sourceware at ryandesign dot com> ---
(In reply to Eli Schwartz from comment #2)
> That repository is an unofficial fork which, if I understand correctly, has
> goals that are in conflict with the original project...

If true, that would be very troubling.

The description of that repository says "This is the official repository for
development of BZip2 1.1+."

It is acknowledged on the BZip2 web site
https://sourceware.org/bzip2/downloads.html where it says "There is also a
experimental future branch which includes a modern build system and an
experimental Rust port. It can be checked out with: git clone
https://gitlab.com/bzip2/bzip2"

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

      parent reply	other threads:[~2024-04-21  2:33 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
2024-04-21  2:33 ` sourceware at ryandesign dot com [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=bug-31660-11876-ucLb4nIQus@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).