From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Last rites for media-video/helixplayer
Date: Mon, 21 Nov 2005 20:29:03 +0100 [thread overview]
Message-ID: <200511212029.15870@enterprise.flameeyes.is-a-geek.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
After realplayer the last week, also helixplayer is pending removal from the
tree.
HelixPlayer, opensource player developed by Real and somewhat similar to
RealPlayer has a bad history of security vulnerabilities and it's still
vulnerable to a security issue (1.0.6 is out but still missing an ebuild).
As the maintainership of this package is difficult, and the package by itself
is a bit of a mess (for example it does only build fine on x86, no way it can
work on amd64 or other platforms AFAICS), I've masked it and it's pending
removal in 24h.
As the release of 2.0 version is imminent [1], and that version *might* work
better on non-x86 arches, the media-video herd reserve the possibility of a
return when that version is released (hopefully with less security concerns).
If someone wants to join the herd for maintaining this package, is absolutely
welcome. Knowing the past problems, if someone wants, it's also invited to
write a maintainer's guide (similar to xine's[2]) so that if it's going to
leave the team someone else will know how to treat it.
[1] https://player.helixcommunity.org/2005/dev/plans.html
[2] http://www.gentoo.org/proj/en/desktop/video/xine.xml
--
Diego "Flameeyes" Pettenò - http://dev.gentoo.org/~flameeyes/
Gentoo/ALT lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-11-21 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 19:29 Diego 'Flameeyes' Pettenò [this message]
2005-11-21 20:15 ` [gentoo-dev] Last rites for media-video/helixplayer Henrik Brix Andersen
2005-11-21 20:43 ` Diego 'Flameeyes' Pettenò
2005-11-21 22:00 ` Edward Catmur
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=200511212029.15870@enterprise.flameeyes.is-a-geek.org \
--to=flameeyes@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