Package Details: fe 1.2.0-1

Git Clone URL: https://aur.archlinux.org/fe.git (read-only, click to copy)
Package Base: fe
Description: AUR helper with a familiar subcommand system
Upstream URL: https://github.com/baris-inandi/fe
Licenses: GPL3
Submitter: baris-inandi
Maintainer: baris-inandi
Last Packager: baris-inandi
Votes: 2
Popularity: 0.000008
First Submitted: 2022-07-31 21:49 (UTC)
Last Updated: 2022-08-15 19:40 (UTC)

Latest Comments

1 2 3 Next › Last »

baris-inandi commented on 2022-08-09 19:48 (UTC)

@yochananmarqos

baris-inandi commented on 2022-08-09 19:47 (UTC)

Should be all good in 1.1.11

yochananmarqos commented on 2022-08-09 19:34 (UTC)

@baris-inandi: I just told you how to update the checksums automatically in my last comment.

Remove the tar xvf fe-$pkgver.tar.gz from your build() function, the tarball is automatically extracted running makepkg.

baris-inandi commented on 2022-08-09 19:24 (UTC)

Also is there any way to change sha256 sums automatically?

baris-inandi commented on 2022-08-09 19:21 (UTC)

@yochananmarqos How does it look now?

yochananmarqos commented on 2022-08-09 18:46 (UTC)

Oh wait, sorry. I forgot this actually isn't a VCS package. This should be using the release tarball. A VCS package would be called fe-git.

Remove the pkgver() function, manually change the pkgver() array to 1.1.6, use the release tarball and clear the value for the md5sums() array:

source=("$pkgname-$pkgver.tar.gz::https://github.com/baris-inandi/fe/archive/refs/tags/$pkgver.tar.gz")
md5sums()

Run updpkgsums or makepkg -g to generate the checksums.

yochananmarqos commented on 2022-08-09 18:39 (UTC) (edited on 2022-08-09 18:39 (UTC) by yochananmarqos)

@baris-inandi: That won't work:

==> Starting pkgver()...
==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: 1.1.6-0-g79e0155

Use the following and remove your prepare() function:

pkgver() {
    cd "$pkgname"
    git describe --long --tags | sed 's/\([^-]*-g\)/r\1/;s/-/./g'
}

Which generates:

1.1.6.r0.g79e0155

Run makepkg -od and you'll see the pkgver is generated.

You do not need to bump the pkgver at all since this is a VCS package. It will always pull from the latest commit and generate the pkgver.

baris-inandi commented on 2022-08-09 18:37 (UTC)

@yochananmarqos

baris-inandi commented on 2022-08-09 18:34 (UTC)

Should I manually bump that manually even if there is a pkgver()?

1 2 3 Next › Last »