From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Cc: pr@gentoo.org, mythtv@gentoo.org
Subject: [gentoo-dev] News Item - MythTV
Date: Fri, 9 Dec 2011 20:38:26 -0500 [thread overview]
Message-ID: <CAGfcS_k7hdYMyc9+XXfWsg9=F2Qf2teYO9BWLt_t=pd9-Ztkrw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
I'm considering sending out this news item in a few days - comments
are welcome. It is a bit different in tone from a typical news item
but MythTV has been in not-so-great shape for a while and my goal is
to reel things in a bit and commit to something we can continue to
maintain, while soliciting help from the community.
Rich
[-- Attachment #2: 2011-12-08-mythtv-updates.en.txt --]
[-- Type: text/plain, Size: 2245 bytes --]
Title: MythTV 0.24.1 Upgrade Author: Richard Freeman <rich0@gentoo.org>
Content-Type: text/plain Posted: 2011-12-08 Revision: 1
News-Item-Format: 1.0 Display-If-Installed: media-tv/mythtv
As many have noticed, the Gentoo version of MythTV has been
significantly lagging the upstream version. We plan to introduce
0.24.1, which is the current upstream stable version, in the next few
days. Before going through the upgrade we wanted to make you aware of
our future plans for MythTV in Gentoo and some of your alternatives.
The Gentoo MythTV package will generally try to stay closer to upstream
than it has in the last year, but probably will only be updated a few
times per year at most. It will benefit from the full Gentoo QA
process, including introduction to ~arch followed by stabilization.
Dependencies will also be controlled in line with Gentoo QA so things
should suddenly not stop working without warning. Versions that are
stabilized will stay in the tree longer after they are superseded for
those who want to take their time with upgrades.
The versions of MythTV in Gentoo may also not support the full range of
upstream plugins.
There is an alternative for those of you who want a more bleeding-edge
experience. Upstream maintains a Gentoo overlay at:
git://github.com/MythTV/packaging.git
The upstream repository will be the first to receive updates and will
have many more intermediate versions including bugfixes. The overlay
also supports all the upstream plugins. However, it is not subject to
Gentoo QA policy - dependencies could stop working or disappear without
warning, and older versions may not be kept around. Generally speaking,
we have not heard complaints from those who use it. Any issues with the
upstream overlay should be reported to the MythTV project and not to
Gentoo bugzilla.
If you're already using the upstream overlay you shouldn't be impacted
by anything done in Portage - your versions will generally stay higher
than our own.
If we drop your favorite plugin and you want it back and are willing to
help maintain it, send us a note at mythtv@gentoo.org. If you're
willing to test it and ensure it works for everybody else, we can keep
it in the portage tree.
next reply other threads:[~2011-12-10 1:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 1:38 Rich Freeman [this message]
2011-12-12 17:03 ` [gentoo-dev] News Item - MythTV Peter Volkov
2011-12-22 4:45 ` Donnie Berkholz
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='CAGfcS_k7hdYMyc9+XXfWsg9=F2Qf2teYO9BWLt_t=pd9-Ztkrw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mythtv@gentoo.org \
--cc=pr@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