From: Stuart Herbert <stuart@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Dropping phpgroupware from the Portage tree
Date: Sun, 20 Nov 2005 11:38:19 +0000 [thread overview]
Message-ID: <1132486700.8602.17.camel@mogheiden.gnqs.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
Hi,
I've just masked the package 'www-apps/phpgroupware', and will be
dropping it from the tree soon. There are a number of issues with the
project, including:
* Outstanding security bugs
* Upstream homepage no longer available
* No real releases in over a year
'www-apps/egroupware' is an actively-maintained fork of phpgroupware,
and is available via Portage for anyone looking for an alternative.
Best regards,
Stu
--
Stuart Herbert stuart@gentoo.org
Gentoo Developer http://www.gentoo.org/
http://stu.gnqs.org/diary/
GnuGP key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319 C549 0C2F 80BA F9AF C57C
--
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-11-20 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 11:38 Stuart Herbert [this message]
2005-11-20 16:49 ` [gentoo-dev] Dropping phpgroupware from the Portage tree Jason Huebel
2005-11-20 18:36 ` Petteri Räty
2005-11-21 8:42 ` Thierry Carrez
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=1132486700.8602.17.camel@mogheiden.gnqs.org \
--to=stuart@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