From: David Leverton <levertond@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Packages up for grabs due iluxa retirement
Date: Mon, 19 Mar 2012 21:00:40 +0000 [thread overview]
Message-ID: <CALc3eMV9VFX0qmP3TPrqR5D0Tv-BK856PHuo2ejBT-CpM7tA9g@mail.gmail.com> (raw)
In-Reply-To: <4F66CC9F.3050007@gentoo.org>
On 19 March 2012 06:05, Samuli Suominen <ssuominen@gentoo.org> wrote:
> dev-cpp/cppserv would need working dev-cpp/sptk and we have none:
>
> http://bugs.gentoo.org/show_bug.cgi?id=402149#c9
>
> the only working versions got marked as "obsolete" by upstream due to
> "undisclosed reasons" whatever that means
>
Not that I personally care, but it seems like this could be "solved"
by just removing fltk support, rather than nuking it completely.
next prev parent reply other threads:[~2012-03-19 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 18:15 [gentoo-dev] Packages up for grabs due iluxa retirement Pacho Ramos
2012-03-19 6:05 ` Samuli Suominen
2012-03-19 21:00 ` David Leverton [this message]
2012-03-19 21:17 ` Samuli Suominen
2012-03-20 1:16 ` Alec Warner
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=CALc3eMV9VFX0qmP3TPrqR5D0Tv-BK856PHuo2ejBT-CpM7tA9g@mail.gmail.com \
--to=levertond@googlemail.com \
--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