Package Details: darling-mach-git r23.44cf244-1

Git Clone URL: https://aur.archlinux.org/darling-mach-git.git (read-only)
Package Base: darling-mach-git
Description: Darling's Linux kernel module (darling-mach)
Upstream URL: http://www.darlinghq.org
Licenses: GPL3
Groups: darling-git
Submitter: Xorg
Maintainer: Xorg
Last Packager: Xorg
Votes: 0
Popularity: 0.000000
First Submitted: 2016-03-02 15:42
Last Updated: 2016-05-04 17:09

Latest Comments

Xorg commented on 2016-05-04 17:12

@jamesan: Ok, that's done. I'll do a similar change in Darling PKGBUILD too. Thank you.

jamesan commented on 2016-05-04 06:24

The version string doesn't follow the VCS package guidelines. For git repos that have "no tags then use number of revisions since beginning of the history" followed by the abbreviated hash commit name with the format:

rREVISION.HASH (i.e. "r23.4036a2b" given the current package version).

Just as the REVISION count only counts revisions that involve the "src/lkm" path of the source, the HASH value should refer not necessarily to the current HEAD commit but rather to the last commit that involved changes under the "src/lkm" path. The prevents unnecessary package upgrades due to version string changes resulting from a commit made upstream that doesn't affect anything under the "src/lkm" path, as the HASH (and version string) should remain unchanged until a commit is made affect code under that path.

This can be done by replacing the latter git-rev-parse command with git-rev-list like so:

git rev-list --abbrev-commit --max-count=1 HEAD -- "src/lkm"

That fetches abbreivated hash of the one commit closest to HEAD under the "src/lkm" path. Putting it all together and adopting the guideline's example use of printf instead of echo, the one pkgver() line (#22) deriving the version string can be:

printf "r%s.%s" "$(git rev-list --count HEAD -- "src/lkm")" "$(git rev-list --abbrev-commit --max-count=1 HEAD -- "src/lkm")"

You can find this all nicely packaged as a patch file here: http://pastebin.com/w46cs7yF

Reference:
https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver.28.29_function

Xorg commented on 2016-03-28 18:32

@wenLiangcan: Ok, it's done. Thank.

wenLiangcan commented on 2016-03-28 07:52

I think darling-mach-dkms-git should be declared providing darling-mach-git

Xorg commented on 2016-03-27 10:11

I've split this package, you can now install DKMS version to avoid to reinstall darling-mach-git after each kernel update.

Xorg commented on 2016-03-02 15:56

About darling-mach-git:
- it needs kernel headers for running kernel
- if kernel headers are found for other kernels (i.e. not-running), the LKM will be build for each of them.