From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org
Cc: Eli Schwartz <eschwartz93@gmail.com>
Subject: [gentoo-dev] Last rites: sci-libs/beagle
Date: Fri, 17 May 2024 05:14:26 +0100 [thread overview]
Message-ID: <87le49f525.fsf@gentoo.org> (raw)
# Eli Schwartz <eschwartz93@gmail.com> (2024-05-17)
# Last updated in 2007, has no reverse dependencies, is unmaintained upstream
# (in 2010 a version 4 alpha was released using cmake, the project has seen no
# other activity upstream). Fails to build with dash, lto.
# Bug #862669, #890423.
# Removal on 2024-06-16.
sci-libs/beagle
reply other threads:[~2024-05-17 4:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87le49f525.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=eschwartz93@gmail.com \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.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