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