[mythtv-users] Missing mythplugins-0.27_p20150904 ebuild in Gentoo tree

[Rich Freeman]

On Tue, Sep 15, 2015 at 2:47 PM, Hika van den Hoven <hikavdh at gmail.com> wrote:
> Thanks for the update. It's as far as I know not an important update
> so I guess waiting a little longer hurts nobody. It is just confusing,
> because world wants to pull in mythtv but then gets blocked.

Yup, because the mythplugins package requires a matching mythtv
version, so emerge holds back the mythtv package to keep them in sync.

> I did check though the Changelog in the mythtv tree and it's from
> june and missing about this last ebuild? So...?

Hmm, I guess automated Changelogs aren't being built after all.  I am
not syncing from rsync so I hadn't noticed.  That is something that
should be working at some point.  The commit history is available in
git.

commit 46a2138cbe071c0199a5b1944d6d7fc45f63f44b
Author: Richard Freeman <rich0 at gentoo.org>
Date:   Thu Sep 10 08:19:41 2015

    media-plugins/mythplugins: fix use syntax error

commit 488e98e28d39cacd78ab112c073a631323f239c4
Author: Doug Goldstein <cardoe at gentoo.org>
Date:   Mon Sep 7 16:06:53 2015

    media-plugins/mythplugins: fix dependencies

    Fixed a number of dependencies including libvorbis and libmp3lame. Fixed
    vorbis depend from bug #554064.

    Gentoo-Bug: 554064

    Package-Manager: portage-2.2.20.1
    Signed-off-by: Doug Goldstein <cardoe at gentoo.org>

commit 866d3312ecb6c48c5d9f48fd7443ef67f3245776
Author: Michał Górny <mgorny at gentoo.org>
Date:   Mon Sep 7 14:24:52 2015

    media-plugins/mythplugins: Remove old to match media-tv/mythtv

    Bug: https://bugs.gentoo.org/show_bug.cgi?id=559898
    Fixes: a9570ca04e081 (Retire a slew of old ebuilds)

    Package-Manager: portage-2.2.20

> I also did look at the new mythweb ebuild and except for the name it
> looks identical. Does it pull a different archive by it's name
> variable? Just interested!

Yup.
MY_PV="${PV%_p*}"
SRC_URI="https://github.com/MythTV/mythweb/archive/v${MY_PV}.tar.gz ->
mythweb-${MY_PV}.tar.gz

The version number is parsed out of the ebuild filename, and then used
to fetch the appropriate tarball.  If there are no changes necessary
to the body of the script, then a version update often just consists
of just copying the file and changing the filename.

For mythtv that is usually only the case moving between minor releases
(such as 0.27.4 -> 0.27.5).  Changes between major releases are more
likely to require more substantial changes to the rest of the script,
and for patches from the fixes branch there is no upstream tarball so
we have to distribute our own and put the filename for that inside the
ebuild.

When I release a new patch to mythtv all I do is diff from the last
release to the current fixes branch, package up the patch in a tarball
named with the last commit ID from mythtv's git, and then publish that
on dev.gentoo.org and stick the git commit ID in the ebuild so that it
gets fetched and applied when it is built.  So if you diff'ed two of
my ebuilds most likely all that changed is an SHA1 from git in a
variable.  Of course, we sometimes fix other bugs at the same time
such as dependency errors, init.d scripts, and so on, so you might see
those changes as well.

If you ever need a new version of some package that isn't in portage,
there is a decent chance that just renaming the existing ebuild will
actually work.

--
Rich