@delx
Would you mind adding a .gitignore
file to the source to ignore artifacts of the build? I believe this would be sufficient:
https://github.com/emerkle826/mythtv/blob/gitingnore/.gitignore
Git Clone URL: | https://aur.archlinux.org/mythtv-git.git (read-only, click to copy) |
---|---|
Package Base: | mythtv-git |
Description: | A Homebrew PVR project (Stable '-fixes' branch) |
Upstream URL: | https://www.mythtv.org/ |
Licenses: | GPL |
Conflicts: | mythtv |
Provides: | mythtv |
Submitter: | JohnLBergqvist |
Maintainer: | JohnLBergqvist |
Last Packager: | JohnLBergqvist |
Votes: | 36 |
Popularity: | 0.000658 |
First Submitted: | 2023-04-10 09:11 (UTC) |
Last Updated: | 2024-06-30 17:31 (UTC) |
« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 31 Next › Last »
@delx
Would you mind adding a .gitignore
file to the source to ignore artifacts of the build? I believe this would be sufficient:
https://github.com/emerkle826/mythtv/blob/gitingnore/.gitignore
@mark.clegg Ah, I didn't notice that the old package had epoch=1. This just means people will need to manually upgrade one time to switch to the new version. I think I'll leave it like that.
@jfabernathy I plan to modify this package to track fixes/32 after MythTV v32 is released. If you want to keep tracking fixes/31 you'd need to fork this package, or maintain your own copy locally.
That version number looks fine to me. It's generated using git-describe. This shows you the number of commits since the v31 tag, followed by 'g' and then the commit hash.
I "upgraded" by "yay -S mythtv Pacman.log says: [2020-10-30T16:31:08-0400] [ALPM] removed mythtv-git (31+fixes.20201012.eb3c84de-1) [2020-10-30T16:31:08-0400] [ALPM] installed mythtv (31+fixes.20201012.eb3c84de-1) However, when I run mythfrontend and look at information center I see: Mythfrontend version: makepkg (v31.0-118-geb3c84de5f-dirty)
Just "upgraded" - Started with a new clone from AUR, built and installed without issues. Just one observation, when installing, pacman thought I was "downgrading" the existing package, which I'm sure is just because of a syntax difference between the apparent version numbers, and is safe to ignore during this transition.
From pacman.log:
downgraded mythtv (1:31.0-3 -> 31+fixes.20201012.eb3c84de-1)
Since I built my latest mythtv build from mythtv-git to get to a more current build of v31, how do I move over to this mythtv package? My goal is to follow a package that stays on V31 and tracks the latest commits, but not move to v32 ever. To me V32 should be new AUR package.
Hi @RuneArch. Sorry but I don't use any of the MythTV plugins so I don't think I'd be a good maintainer for that package. I'm happy to work with any maintainer to help these packages work well together.
This package now tracks the MythTV fixes/31 branch. There are quite a few upstream bugfixes since the v31 release.
Thanks to Taijian and all the previous maintainers for their efforts.
Whenever a commit is made by MythTV's git upstream you can rebuild this package without waiting for an update. Please don't flag it as out of date just because there's a new commit. Occasionally I'll push updates manually to stop the version from looking too old. I'll also push updates whenever a packaging change is needed for the build to work.
Just to add... are you taking ownership of mythplugins too?
Just chiming in with my support @delx - thanks!
@delx I would be grateful for this (How would people feel about me adopting this modifying it to track the fixes/31 branch) and offer my entire cache of encouragement :)
Pinned Comments
JohnLBergqvist commented on 2023-04-10 15:56 (UTC) (edited on 2023-04-10 15:57 (UTC) by JohnLBergqvist)
This package replaces the previous 'mythtv' AUR package. It has been renamed to comply with Arch's VCS package guidelines.
I hope to update the various mythplugins AUR packages soon