search

TheBluWiz / H265Repack

easily repack videos to HEVC
GNU General Public License v3.0
6 stars 0 forks source link

AUR Package #3

Open username227 opened 1 month ago

username227 commented 1 month ago

OK so here's my draft for an AUR package. I am not really a developer, but I like to take projects and make AUR packages for them. This package is a git package, which will self-update after each commit is pushed to github on the "main" branch. After you have a better system for release #'s, we can do a second package, pulling the download directly from the release source code. Such a package would need to be manually updated after each release, unless you institute an auto-update (which is probably more work than it's worth, since updating the package isn't hard).

Let me know what you think. PKGBUILD.txt

TheBluWiz commented 1 month ago

I'm currently letting GitHub handle release versions and have created 2 "release" versions. We are currently at v1.1.0. When release versions are created they are available via a zip file or a tar ball. I occasionally may update the main branch for simple things like README clarifications and wouldn't want each of those to push updates to people. So I am somewhat hesitant to set it to update based off of main branch commits.

Can you set this to go based off of tagged releases rather than commits? I am unfamiliar with creating AUR packages, and can't make time immediately to research it.

username227 commented 1 month ago

OK so you're more interested in the second paackage. that's fine. i'll tweak it. but i was confused about the packge numbering because your latest release doesn't say 1.1.0, it says undateable or something like that.

username227 commented 1 month ago

PKGBUILD.txt This is a standard release package. It would drop the git name and needs to be updated for each release. The updates are simple and would only take two minutes (and I'd be happy to help out to maintain it). The only way I can think of to create a git package that updates automatically with each release would be to create a third branch called "release" or something and only pull releases into this branch. (but i am not an expert compared to others).

username227 commented 1 month ago

I take it back. Just tested. I changed "branch" to tag and it worked just fine. This package would still need to be manually updated, though, to update the tag function for each release. so once we're doing that, the first package makes more sense because it's a simpler build and doesn't require cloning the entire repository. Notice PKGBUILD.txt