[mythtv-users] [mythtv-commits] Ticket #10792: Please bump Gentoo ebuilds to 0.25

[Karl Newman]

On Mon, Sep 24, 2012 at 8:28 PM, lists.md301 <lists.md301 at gmail.com> wrote:

>
>
> On Fri, Sep 21, 2012 at 2:43 PM, Karl Newman <newmank1 at asme.org> wrote:
>
>> On Fri, Sep 21, 2012 at 2:40 PM, lists.md301 <lists.md301 at gmail.com>wrote:
>>
>>> On Fri, Sep 21, 2012 at 12:07 AM, Karl Newman <newmank1 at asme.org> wrote:
>>>
>>>> I had given up on portage for mythtv but I just checked this out. The
>>>> myth plugins are handled differently now. Instead of installing mythmusic,
>>>> mythnetvision, etc., you just install the single media-plugins/mythplugins
>>>> package and enable the USE flags for the specific plugins you want. That
>>>> seems like a much simpler and better method, and closer to how upstream
>>>> distributes them. So in order to upgrade you'll probably have to manually
>>>> uninstall your media-plugins/myth* packages, set up your USE flags in
>>>> /etc/portage/package.use, then upgrade mythtv and install the mythplugins
>>>> package.
>>>>
>>>
>>> So is this documented any place "official" (like other than your
>>> email)?  I know I only found the interim Gentoo Portage from git directions
>>> from the mailing list archive (back around 0.23->0.24, during that period
>>> when the actual Gentoo support had gone stale), and I was really wondering
>>> how Gentoo ebuilds were being handled.  For myself, I'm still at 0.24-fixes
>>> and will probably just wait until there is some stability with the eventual
>>> 0.26-fixes before attempting any upgrade.
>>>
>>
>> I'm sure there's nothing "official" for either Gentoo or MythTV about
>> switching from an overlay package to a portage package. Sorry if gave you
>> the impression I was involved with this change. I just looked at the new
>> packages based on your prompting and figured out what had changed and what
>> you needed to do to switch.
>>
>>
> I didn't mean that you were in any way responsible--I had been thinking
> about sending an email about this for a while, and your comment was as good
> an opportunity as any.  Thank you for the contents of your reply.  I was
> fishing for something authoritative from the responsible developer(s), or
> direction to where that might be.  I had seen the IRC conversation between
> wagnerrp and cardoe, so I knew something was brewing on for the main
> portage tree.  Since ebuild generation became part of the github repository
> (for 0.24, anyway), I was hoping there was some comment somewhere, in a
> ticket or mailing that I might not have seen, as to what is the
> "recommended" Gentoo update/migration method, or if it was officially
> deprecated/abandoned.  And if there is nothing official, then at least
> other user experiences for those more adventurous to take the plunge.
>
> When I brought new master backend hardware (more SATA ports for my disks!)
> online last year coinciding with my update to 0.24, I did have parallel
> production/test systems to shake things out...that's when I moved from the
> official portage ebuilds to the overlay/git ones.  Lacking that alternate
> hardware now, when the time comes, I'll probably do what I have done
> previously, (having learned my lesson with an difficult Gentoo expat update
> years back), and clone my root partition to another on my master, reboot
> into it (yeah, I suppose I could run chroot) and do my emerging there, with
> the backend shut down, so there's no database discontinuity/orphaned
> recordings to import.
>

Sorry I haven't migrated yet so I have no notes for you; I'm waiting for
the gentoo ebuilds to pass my recent git-updated version. Well, that and
also to get back home again. I seem to recall suffering the expat problem
too (one or two other sticky situations), but generally for me Gentoo has
been really stable and easy to manage. I stick to the stable packages for
the most part and only keyword the packages where I want the latest
version. I emerge --sync and emerge -uND @world just about every day so I
update things as they are released to stable. That keeps the package
changes incremental, so that if I encounter a problem or need to edit some
config files I can deal with it in bite-sized chunks instead of a huge
batch of things that may all break at once.

Thanks for letting me know about the excellent epatch_user functionality.
I've been using Gentoo for ~7 years with this Myth system, and I'm *still*
learning new and awesome things.

Karl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20120925/9d7a6da8/attachment.html>