Package Details: readest-deb 0.9.55-1

Git Clone URL: https://aur.archlinux.org/readest-deb.git (read-only, click to copy)
Package Base: readest-deb
Description: Modern, feature-rich ebook reader designed for avid readers offering seamless cross-platform access, powerful tools, and an intuitive interface
Upstream URL: https://github.com/readest/readest
Licenses: AGPL-3.0-or-later
Conflicts: readest, readest-bin, readest-git
Provides: readest
Submitter: MareDevi
Maintainer: MareDevi
Last Packager: MareDevi
Votes: 3
Popularity: 0.41
First Submitted: 2025-04-20 03:40 (UTC)
Last Updated: 2025-06-07 06:37 (UTC)

Pinned Comments

MareDevi commented on 2025-04-20 15:48 (UTC) (edited on 2025-04-20 15:48 (UTC) by MareDevi)

This package has been renamed from readest to readest-deb

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

MareDevi commented on 2025-01-04 09:25 (UTC)

@kseistrup I've recieved it and updated the pkgbuild
thanks for your help very much!

kseistrup commented on 2025-01-04 09:00 (UTC)

@MareDevi You may unintentionally have beebn caught in a firewall rule. I've sent a copy to your email address.

MareDevi commented on 2025-01-04 05:27 (UTC)

@kseistrup thanks, but is the link still effective? I can't open it in my browser

kseistrup commented on 2025-01-03 08:13 (UTC)

@MareDevi, please take a look at https://s.nyf.dk/8p94m/

I have cleaned up the PKGBUILD, added missing libraries and removing unnecessary ones, added a sha256sum, removed unused architectures, improved quoted environment variables, and added a Maintainer tag.

I opted to put dependencies on individual lines in their array, so that it is easier to add/remove elements and still keep the array sorted.

MareDevi commented on 2025-01-01 12:11 (UTC)

@kseistrup Thank you so much for your help, I learned a lot from it! I wish you a happy 2025 as well!

kseistrup commented on 2025-01-01 11:55 (UTC)

PPS: And you can even run namcap on the final binary package to see if it complies to the ArchLinux specification.

kseistrup commented on 2025-01-01 11:41 (UTC)

PS: If you run

namcap PKGBUILD  # from the “namcap” package

you will know if your PKGBUILD is compliant. Beware, though, that not all of the warnings from namcap are relevant, but it can save you from some big blunders.

And running

rua shellcheck PKGBUILD  # from the “rua” package

will check that the shell syntax in the PKGBUILD file is correct (PKGBUILD is just a bash script).

kseistrup commented on 2025-01-01 11:36 (UTC)

@MareDevi Thanks for learning.

One more change: The binary in the package is not stripped (because of the !strip option). It seems to run perfectly fine when stripped, so you could remove the '!strip' from the options=(…) array, bump the pkgrel and push the changes again. It should save some storage bytes.

I think that's all I have to say, the you can enjoy a happy 2025. :)

Thanks for packaging this.

MareDevi commented on 2025-01-01 11:16 (UTC)

@kseistrup Oh I understand! Thank you so much, I have always thought that PKGREL and PKGVER are all related to the upstream version🤣

kseistrup commented on 2025-01-01 11:09 (UTC)

@MareDevi

Okay, one more thing: Every time you change anything in the PKGBUILD file you need to bump/increase the pkgrel variable, regenerate the .SRCINFO file, and then commit the changes and push them to AUR. Otherwise AUR helpers like yay will not know that the package has been updated.

So the pkgver variable should always reflect the app version, and the pkgrel variable is for signalling a change in the PKGBUILD.

You can rwead all about the PKGBUILD format in PKGBUILD(5) (type “man 5 pkgbuild” in a terminal emulator).

Cheers.

« First ‹ Previous 1 2 3 Next › Last »