Package Details: bracmat-git 6.14.2.r274-1

Git Clone URL: (read-only, click to copy)
Package Base: bracmat-git
Description: Programming language for symbolic computation with pattern matching features
Upstream URL:
Keywords: json xml
Licenses: GPL2
Conflicts: bracmat
Provides: bracmat
Submitter: xtradev
Maintainer: xtradev
Last Packager: xtradev
Votes: 0
Popularity: 0.000000
First Submitted: 2020-05-01 12:27 (UTC)
Last Updated: 2023-04-04 11:38 (UTC)

Latest Comments

xtradev commented on 2020-06-24 13:57 (UTC) (edited on 2020-06-26 02:48 (UTC) by xtradev)

Git metadata in the current Bracmat repository contains no useful information - there is only one (stale or irrelevant) tag - so for now I decided to stick to the format I am using. As I understood the gist of the referenced wiki-page, "REVISION is a monotonically increasing number that uniquely identifies the source tree". The best source of such information, in my opinion, is the BUILD variable in the src/bracmat.c file. The pkgver variable in PKGBUILD missed a period before r, I added it.

katt commented on 2020-06-23 17:46 (UTC) (edited on 2020-06-23 17:50 (UTC) by katt)

Just simply using the first example listed here should be fine

EDIT: Second one should be fine, getting the latest released version + commits and also chopping off the "V.":

git describe --long --tags | sed 's/^V.//;s/\([^-]*-g\)/r\1/;s/-/./g'

xtradev commented on 2020-06-23 14:03 (UTC) (edited on 2020-06-23 14:07 (UTC) by xtradev)

Thank you for pointing that katt, I cleaned up makedepends. What would you consider the revision in this case? I think I do not use the commit - I use the BUILD number as the revision. Isn't it appropriate? I extract it along with version number from src/bracmat.c

katt commented on 2020-06-23 11:50 (UTC)

Neither gcc, make or sed should be listed as makedepends since they're in the base-devel group. Also your pkgver should include the revision since only listing the commit will result in pacman not picking up new commits as an update.