From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] divx4linux sudden death
Date: Sun, 30 Oct 2005 19:58:01 +0100 [thread overview]
Message-ID: <200510301958.09011@enterprise.flameeyes.is-a-geek.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
Okay another package that we're shortening life's.
Why that? Well divx4linux is masked since 21 october, enough time to know that
is going to be removed. It's also broken for recent x86 architectures, and
it's x86 only.
All the useflags divx4linux are going to fade away, so you'll probably want to
do an emerge --newuse world to make sure that the packages get updated.
Also drip 0.8 (stable version) is going away as it's depending scricly on
divx4linux.
I'll start the clean after having dinner.
--
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-10-30 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 18:58 Diego 'Flameeyes' Pettenò [this message]
2005-10-30 20:09 ` [gentoo-dev] divx4linux sudden death Peter Ruskin
2005-10-30 20:22 ` Diego 'Flameeyes' Pettenò
2005-11-09 3:23 ` Mike Frysinger
2005-11-09 9:27 ` Luca Barbato
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=200510301958.09011@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