Package Details: mpv-bash-completion-git 8:3.3.18-1

Git Clone URL: (read-only, click to copy)
Package Base: mpv-bash-completion-git
Description: Bash completion for the mpv video player
Upstream URL:
Keywords: bash mpv
Licenses: GPL
Conflicts: mpv-bash-completion
Provides: mpv-bash-completion
Submitter: 2ion
Maintainer: 2ion
Last Packager: 2ion
Votes: 23
Popularity: 0.109967
First Submitted: 2015-03-12 15:14
Last Updated: 2020-01-11 12:51

Latest Comments

« First ‹ Previous 1 2

2ion commented on 2016-03-06 04:55

@sekret: Sorry about the version number messup; I forgot to push the last change to the PKGBUILD last night which normalized versioning.

As for the (ab-)use of the epoch field: Until the introduction of hooks, the package needed to be rebuilt manually for any update to mpv that changed the set of available options. In order to be able to see if the currently installed completion was out-of-date, the pkgver was set to the version of the mpv package the completion was generated from. Accordingly, whenever I made a substantial improvement to the upstream source or the PKGBUILD (both of which I own, and I'm using the PKGBUILD to install it on my system) I'd liked to push to every user, I'd increment the epoch in order to force rebuilds as I couldn't know what actual version number the package on users' systems would have. The weird package number you saw earlier was the version from my own mpv package mpv-legacy-af-git, a slip-up.

From now (epoch 8) onward, with hooks for triggering rebuilds having been made available and implemented here, versioning will (roughly) follow packaging guidelines. pkgver is now a static field.

sekret commented on 2016-03-05 23:49

And how did you come up with this pkgver 0.16.0+1 ??? When I run makepkg on your PKGBUILD, I get 0.16.0 , so what is this "+1" ??? With this pkgver you provide cower always reports your package as outdated on my machine, although I'm up to date.

sekret commented on 2016-03-05 19:02

One quick question: Why do you use epoch so much? epoch is supposed to be used for e.g. forced downgrades, so pacman or yaourt or whatever still "sees" it as an "update". You seem to use it all the time, which is really not necessary! As long as $pkgver-$pkgrel goes up, there's no need to bump epoch!

2ion commented on 2016-03-05 14:47

From epoch 4 onward, we utilize pacman/libalpm hooks for generating the completion file both after installing this completion package for the first time and also automatically whenever you update mpv.

Because there are various flavours of mpv around when including the AUR, the rebuild trigger acts on all packages matching 'mpv' and 'mpv-*'. This is due to the libalpm trigger not being able to act on packages which just 'provide' mpv.

In my opinion, this solution works well enough.

2ion commented on 2016-02-07 11:42

Reflected changes in recent versions of mpv which should fix a lot of erroneous completions.

2ion commented on 2015-09-10 11:50

Fixed by stripping the epoch from the installed mpv package's version.

SammysHP commented on 2015-09-10 10:46

pkgver() is broken.

==> Starting pkgver()...
==> ERROR: pkgver is not allowed to contain colons, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: 1:0.10.0