On 08/22/2017 07:18 AM, Rich Freeman wrote: > On Tue, Aug 22, 2017 at 6:34 AM, Nils Freydank <nils.freyd...@posteo.de> > wrote: >> >> BTW, mythtv has no maintainer, might you be interested in a proxied >> maintainership? >> > > I'd encourage somebody to step up and do this - I no longer use it and > MythTV is one of those packages that you really need to use if you > want to maintain it (hardware/etc, plus a fair bit of work). > > If somebody steps up and wants tips please do feel free to ping me, > and I suspect cardoe would also be willing. > > In general though upstream maintains git branches for each of their > releases under fixes/ that track stuff like this. This commit was in > fixes/0.28. These are stable branches and very unlikely to break > anything - and this was the basis of all the updates within a release > on Gentoo previously. The minor releases like 0.28.1 are just tagged > versions off of these branches - 0.28 plus all the fixes up to that > point in time is basically the same as 0.28.1. The ebuild is designed > to make it easy to pull these in - I see that cardoe pointed it at > github so in theory you can just change the hash to the new head and > it will probably pull in all the fixes. > > They're up to 0.29 now. That isn't in the 0.28 fixes branch, and > might need a bit more testing. >
I use mythtv on a daily basis, have multiple frontends connecting to a remote backend, but I do not know if the skills I have are enough to even proxy-maintain them, or I'd offer in a heartbeat. The only times I've delved into ebuilds is when they don't work, and my knowledge is quite limited there. Dan
