Age | Commit message (Collapse) | Author |
|
The package version function for all templates including
source-git-plain broke since pacman reversed the order in which pkgver
and prepare are run. The commit "run pkgver() in srcdir" partially
restored it to a working state in which the version number was found.
However, since the prepare function still removed the git directory, no
revision number and commit hash could be appended in the pkgver function
running afterwards.
Now that the git directory does not not end up in the package any more
because of the recent exclusion of hidden files from installation, it
can be left present for the pkgver function to use without containing
any further process.
|
|
This reverts "add mksrcinfo header".
The .SRCINFO is now generated by "makepkg --printsrcinfo" which does no
longer include any header since commit f63854f [1], released with pacman
version 5.0.1.
[1]: https://projects.archlinux.org/pacman.git/commit/?id=f63854fa96f658ca5bdf2c21a1cd33cf4e3fbdbd
|
|
Since pacman version 5.0.1, prepare() runs before pkgver(). Restoring
the function to a working state actually saves a directory change as
they now find the sources already moved down.
|
|
Other packages usually depend on the package without any -git suffix.
This makes it possible to als satisfy these dependency requirements when
they target specific versions or version ranges.
|
|
With the newest release, the original maintainer has now tested the
extension with the current Firefox version and decided to declare it as
compatible, eliminating the reason to source from a fork.
Switching back makes the package incorporate upstream updates again.
|
|
The new version of mksrcinfo released with the recent update to
pkgbuild-introspection adds a header to all .SRCINFO files.
|
|
The maintainer of the original source, swick, has not yet merged the
pull request for Firefox 40 while Firefox 41 is already out. The Add-On
seems to work mostly fine with the current version also, so switching to
a fork that raising the maxVersion to a ridiculously high 50 should be
fine until the original upstream updates.
|
|
|