Package Details: protonhax-git 1.0.5-1

Git Clone URL: https://aur.archlinux.org/protonhax-git.git (read-only, click to copy)
Package Base: protonhax-git
Description: Program to help executing outside programs in proton
Upstream URL: https://github.com/jcnils/protonhax
Licenses: BSD
Submitter: JcNils
Maintainer: JcNils
Last Packager: JcNils
Votes: 3
Popularity: 0.000040
First Submitted: 2022-03-22 17:34 (UTC)
Last Updated: 2024-04-11 00:41 (UTC)

Dependencies (1)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

Freso commented on 2024-06-12 22:00 (UTC)

A few changes from the non-git package you might want to adopt: https://gitlab.archlinux.org/freso/protonhax/-/compare/d1171778847628c28023d9f8e33d12b3fa7369ab...408272aa7d856958a8ffbd91aef5a7386a13cfa4?straight=false (If you’re familiar with working git, you can pull in either the "protonhax" repository here from AUR or from the Arch GitLab and merge or cherry-pick the changes, if you want.)

Also, please add a conflicts and provides for "protonhax", per https://wiki.archlinux.org/title/VCS_package_guidelines#Conflicts_and_dependencies :)

JcNils commented on 2024-04-11 01:07 (UTC)

Thank you so much kusoneko! I updated the makedepends as instructed.

There was also an upstream update to remove the compiler, everything is bash script now.

kusoneko commented on 2024-04-08 01:09 (UTC)

Hello,

Please include git in the makedepends as stated in the AUR VCS packaging guidelines. Currently, it doesn't compile in a clean chroot without it.

Thank you.

JcNils commented on 2022-04-09 20:19 (UTC)

Thank you very for explaining it to me, Freso.

First package I manage and there are so much to learn.

Freso commented on 2022-04-09 17:02 (UTC)

I cannot find how to update the pkgver from the PKGBUILD with the new tags, as the pkgver() only kicks in when I build the package.

You’re not supposed to. :) Only update the PKGBUILD when something in the build process needs changing, otherwise the pkgver() function will make sure that the locally installed version of the package always reflect the installed version.

JcNils commented on 2022-03-22 18:22 (UTC)

I am not sure how to change this into a git, when I add the -git it generates a new package https://aur.archlinux.org/packages/protonhax-git

Thanks for the guidelides, I also used this proto file https://gitlab.archlinux.org/pacman/pacman/blob/master/proto/PKGBUILD-vcs.proto#L33

I cannot find how to update the pkgver from the PKGBUILD with the new tags, as the pkgver() only kicks in when I build the package.

JcNils commented on 2022-03-22 17:17 (UTC)

I fixed the PKGBUILD. I will make it into a -git package. Thank you for letting me know about that mistake, and for the guidelines, there are helpful.

Freso commented on 2022-03-20 09:51 (UTC)

Also, this should be a -git package since it always builds the latest from the git repository. See https://wiki.archlinux.org/title/VCS_package_guidelines

If you want to have "stable" releases, you should tag them in the repository and specifically pull those for building the package.

Freso commented on 2022-03-20 09:48 (UTC)

Looks like you committed (and pushed) an updated .SRCINFO but didn’t also commit (and push) the corresponding PKGBUILD.

Sk1t commented on 2022-03-18 00:32 (UTC)

The AUR reports v4 but it builds v3.

1 2 Next › Last »