Package Details: pensela-bin 1.2.5-1

Git Clone URL: (read-only, click to copy)
Package Base: pensela-bin
Description: The Swiss Army Knife of Screen Annotation Tools
Upstream URL:
Keywords: annotation electron screenshot
Licenses: ISC
Submitter: waliwaqars
Maintainer: waliwaqars
Last Packager: waliwaqars
Votes: 3
Popularity: 0.002142
First Submitted: 2021-09-22 05:53 (UTC)
Last Updated: 2021-12-21 11:25 (UTC)

Latest Comments

waliwaqars commented on 2021-09-22 08:05 (UTC)

I can only assume you already have made a typical PKGBUILD for your pre-packaged release, so why not upload that instead?

If that was the case, what you said would be 100% the way to do it. However, I'm using electron-builder to package my app for multiple platforms (and automatically deploy to GitHub), and it simply gives you a prebuilt binary. The ".pacman" extension is it's doing too and is simply there to distinguish between packages for different platforms.

Also, thanks for the command you mentioned, that's really useful, and I'm glad you like the project. :)

Cynthetika commented on 2021-09-22 07:58 (UTC) (edited on 2021-09-22 08:04 (UTC) by Cynthetika)

Hi waliwaqars!

Sorry to "nitpick" but your current AUR package is repackaging a pacman package you've already made! While I can't see why the current PKGBUILD you've uploaded wouldn't technically work (I haven't tested it) - it just doesn't really make sense to do it this way! =)

I can only assume you already have made a typical PKGBUILD for your pre-packaged release, so why not upload that instead? Otherwise - re-packaging a binary is fine but this is an amusing way to do it (twice)! =D I'm not sure how familiar you are with Arch-based distributions, so here's a typical explanation (although again, I'm guessing you know this?):

AUR packages create a pacman package to install - not provide some kind of pre-packaged binary definition. Typically, PKGBUILD file would contain commands to either:

  • build and package your Pensela application from source, such as:

    .1. from a source-code archive/tagged git repository (typically with no suffix),

    .2. from a git master/development branch (typically with a "-git/-devel" suffix), or

    .3. both in two separate AUR packages (if there is enough demand and frequent commits to warrant a "development/beta" version)

  • just download and package a pre-built binary from an alternative form (such as extracting from the Appimage or Debian package you've uploaded to the project Github Release section)

I see in the repository 'readme' you direct people to use either this AUR "package" or to just download and install the pre-packaged pacman file (although note that the "Arch Way" would be using the PKGBUILD as explained above instead of a pre-packaged binary =P ). BTW, for internet-connected users on the current Pacman version, you could just direct users to install in one step with (this is also where a 'latest' version tagged URL is handy):

$ sudo pacman -U ''

Also, while not technically necessary I'd recommend leaving the .pkg.tar.xz file extension on your pre-packaged pacman releases on Github (if the user is cheeky like me and doesn't read the repository 'readme' it's not immediately obvious what that file is with just a .pacman extension despite the name).

Anyway - thanks for developing (and open-sourcing) your very nice cross-platform screen annotation utility! It is very nice! =)