From: "Tony \"Chainsaw\" Vroon" <chainsaw@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Cc: eric@brouhaha.com
Subject: [gentoo-dev-announce] Last rites: sys-apps/lcdtest
Date: Thu, 12 Aug 2010 14:31:33 +0100 [thread overview]
Message-ID: <1281619893.3326.10.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
While this should be a fairly simple package to maintain, people
insist on breaking the underlying libraries it depends on:
http://bugs.gentoo.org/show_bug.cgi?id=293091
http://bugs.gentoo.org/show_bug.cgi?id=297335
http://bugs.gentoo.org/show_bug.cgi?id=328137
Things did not improve when upstream then switched to a build system
so broken it was easier to hand-crank things in the ebuild (scons).
I will be masking this package by the end of this week for removal in 30 days.
If you want, go get it and take my name out of metadata.xml; personally I've had
enough of it. I believe a newer 1.18 version is out that you could bump the ebuild to.
Thanks in advance if you decide to take on this challenge.
Regards,
Tony V.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2010-08-12 13:56 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=1281619893.3326.10.camel@localhost \
--to=chainsaw@gentoo.org \
--cc=eric@brouhaha.com \
--cc=gentoo-dev-announce@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