Package Details: poe 1.4.2-1

Git Clone URL: https://aur.archlinux.org/poe.git (read-only, click to copy)
Package Base: poe
Description: .po file editor
Upstream URL: https://strahinja.srht.site/poe
Keywords: gettext po tui
Licenses: GPL3
Submitter: strajder
Maintainer: strajder
Last Packager: strajder
Votes: 0
Popularity: 0.000000
First Submitted: 2021-10-07 15:08
Last Updated: 2022-01-14 19:13

Dependencies (0)

Required by (0)

Sources (1)

Latest Comments

strajder commented on 2021-10-07 22:11

I have found some information here, though not directly related to AUR:

https://semver.org/#is-v123-a-semantic-version

“v1.2.3” is not a semantic version. However, prefixing a semantic version with a “v” is a common way (in English) to indicate it is a version number. Abbreviating “version” as “v” is often seen with version control. Example: git tag v1.2.3 -m "Release version 1.2.3", in which case “v1.2.3” is a tag name and the semantic version is “1.2.3”.

Since I'm updating PKGBUILD manually, I could drop the "v" in pkgver, but I will keep it in git tags. Thanks for the input.

FabioLolix commented on 2021-10-07 19:52

Well, for VCS pkgbuilds is it said to cut prefixes https://wiki.archlinux.org/title/VCS_package_guidelines#The_pkgver()_function , seems it isn't specified for stable pkgbuilds, however there isn't one package in the official repository that have a prefixes, you can do as you wish until it specified

strajder commented on 2021-10-07 18:47

Can you link to the requirement that pkgver mustn't contain 'v'? I'm looking at the Arch wiki, which states that it can contain letters, among other things:

https://wiki.archlinux.org/title/PKGBUILD#pkgver

It can contain letters, numbers, periods and underscores, but not a hyphen (-).

Re: gzip: okay, I will remove it completely then.

FabioLolix commented on 2021-10-07 17:31

'v' doesn't have to be or mustn't be in pkgver?

mustn't be in pkgver=

I chose to put 'v' in git tags in my projects

In your project you can do what you want, the 'v' and other prefixes can (and need to be) removed from the packages, it is easy to do and is packages duty.

gzip is used by default.gz.do (called by all.do) redo script to compress documentation when building poe. You could say it is a build dependency, so I guess I should move it to makedepends then.

gzip is part of base-devel too

strajder commented on 2021-10-07 17:15

'v' doesn't have to be or mustn't be in pkgver? I chose to put 'v' in git tags in my projects, since I've seen a number of projects do the same. Not sure about AUR though, since I've just recently made AUR packages for a number of my programs, including poe.

About gcc, I didn't know that, since I'm new to publishing packages on AUR.

gzip is used by default.gz.do (called by all.do) redo script to compress documentation when building poe. You could say it is a build dependency, so I guess I should move it to makedepends then.

FabioLolix commented on 2021-10-07 16:55

Hello, the 'v' don't have to be in pkgver=

packages needed to build the pkgbuild that are in the base-devel group don't have to specified, gzip is not used by makepkg since iy use bsdtar from libarchive

According to namcap (and ldd) gcc and gzip are not needed to run the program