You are not logged in.

#1 2025-03-22 21:35:57

jullang
Member
Registered: 2025-03-22
Posts: 4

PKGBUILD for AnymeX

As I couldn't find one yet, I made a PKGBUILD for AnymeX, and as this is the first time I'm doing something like this, the arch wiki recommends I search for some reviews, so here we are! If anything could be improved about this, or even better, if there isn't, please let me know!

Last edited by jullang (2025-03-22 21:54:05)

Offline

#2 2025-03-22 21:50:08

mackin_cheese
Member
Registered: 2025-01-07
Posts: 351

Re: PKGBUILD for AnymeX

jullang wrote:

As I couldn't find one yet, I made a PKGBUILD for AnymeX, and as this is the first time I'm doing something like this, the arch wiki recommends I search for some reviews, so here we are! If anything could be improved about this, or even better, if there isn't, please let me know!

What's gitbub? i never heard of it

Offline

#3 2025-03-22 21:54:45

jullang
Member
Registered: 2025-03-22
Posts: 4

Re: PKGBUILD for AnymeX

yeah me neither, don't know how that got in there yikes

Offline

#4 2025-03-22 22:05:03

Scimmia
Fellow
Registered: 2012-09-01
Posts: 12,521

Re: PKGBUILD for AnymeX

provides=("$pkgname=$pkgver")
conflicts=(anymex)

This is nonsense. It doesn't provide $pkgname, it *is* $pkgname, and you're saying it conflicts so it can't be installed at the same time as itself?
This can make sense if the pkgname is different, which it actually should be. If you're not building from source and the source is available, the pkgname should be anymex-bin.

_appimage=$_PkgName.AppImage
source=($_appimage::$url/releases/download/v${pkgver//_/-}/$_PkgName-Linux.AppImage)

You need to rename the source to something that's going to be unique for each version. Typically with this problem, running makepkg on each update would throw an error. At least it would if you weren't skipping the checksum, which you absolutely should not do. Right now, it would happily build the old version and put the new pkgver on it.

What, exactly, are you doing with that wrapper script? And then putting things in /usr/bin/lib and /usr/bin/data, hell no. None of this makes sense.

mv $srcdir/squashfs-root/usr/bin/data/*

You should be using cp, not mv, and you didn't quote this path, same for the other mv.

You didn't install the license, which is required for MIT.

Last edited by Scimmia (2025-03-22 22:19:43)

Offline

#5 2025-03-22 22:28:28

jullang
Member
Registered: 2025-03-22
Posts: 4

Re: PKGBUILD for AnymeX

Thank you for the feedback, should be all cleaned up now!

Last edited by jullang (2025-03-22 22:40:12)

Offline

#6 2025-03-22 22:43:48

Scimmia
Fellow
Registered: 2012-09-01
Posts: 12,521

Re: PKGBUILD for AnymeX

There is no standard MIT license, that's the problem. The copyright line is changed for every person using it. You'd have to pull it from the repo, but make sure to do it from the same version as the binary, not from master/main

Offline

#7 2025-03-22 22:53:40

jullang
Member
Registered: 2025-03-22
Posts: 4

Re: PKGBUILD for AnymeX

Done, thank you!

Offline

Board footer

Powered by FluxBB