Package Details: crema-git 3.1.1-1

Git Clone URL: https://aur.archlinux.org/crema-git.git (read-only, click to copy)
Package Base: crema-git
Description: Manage (remote) custom repositories
Upstream URL: https://gitlab.com/mipimipi/crema
Licenses: GPL3
Conflicts: crema
Provides: crema
Submitter: mipi
Maintainer: mipi
Last Packager: mipi
Votes: 2
Popularity: 0.000350
First Submitted: 2019-05-12 05:24 (UTC)
Last Updated: 2022-08-27 11:51 (UTC)

Pinned Comments

mipi commented on 2023-01-29 08:00 (UTC)

crema will no longer be maintained. Please us repman instead.

Latest Comments

mipi commented on 2023-01-29 08:00 (UTC)

crema will no longer be maintained. Please us repman instead.

haawda commented on 2021-01-26 17:56 (UTC)

provides=(crema-git) is useless. Each package provides itself.

provides=('crema') would make sense.

mipi commented on 2019-06-08 23:32 (UTC)

@Kr1ss: Done.

Kr1ss commented on 2019-06-08 17:14 (UTC)

Sorry to bother you again, but the pkgver() function broke. Turns out it wasn't my best idea to suggest using git describe, which only works as expected when the HEAD commit is tagged.

Would you be so kind to change the printf statement to something like

printf "r%s.g%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"

which should work anyways ? Thx !

Kr1ss commented on 2019-05-21 10:56 (UTC)

Fine, thx for the quick response and update !

mipi commented on 2019-05-21 05:00 (UTC)

Hi @Kr1ss, thanks for the hint. I've adjusted the PKGBUILD accordingly. Cheers, mipi

Kr1ss commented on 2019-05-20 20:38 (UTC) (edited on 2019-05-20 22:30 (UTC) by Kr1ss)

Hello @mipi,

first of all, thx a lot for packaging this for the AUR, and for writing the script in the first place ! I would have a request though. Since this is a -git package, it is supposed to have a dynamic $pkgver, which u can achieve by implementing an additional function similar to :

pkgver() {
  cd "$srcdir/$_pkgname"
  printf "%s.r%s.g%s" "$(git describe)" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
}

At the current upstream status, this results in 1.1.r26.g64d3690, so it represents the current release tag, the commit number and the last commit's sha1 hash; and it will automatically be updated on a package rebuild after a new upstream commit. Of course u could change this to your liking, but I would appreciate some kind of dynamic versioning.

EDIT : Another thing. I guess you should change the first install command in the package() function to something like

install -Dm755 -t "$pkgdir/usr/bin/" "$_pkgname"

b/c your current PKGBUILD doesn't try to install the script in the /usr/bin/ folder but as /usr/bin, obviously conflicting w/ quite every other package... ;-)

Thx again, have a great one ! Cheers !