| Age | Commit message (Collapse) | Author |
|---|
|
To improve readability, related functionality should be kept together,
while different section are separated by multiple newlines.
|
|
Despite the information given out via the API, Firefox actually permits
installation of some extensions reported incompatible, which then work
fine. This is because Firefox' internal mechanism determines that these
extensions should be compatible by itself and subsequently refrains from
even querying the API to begin with.
The version range in the depends array should reflect this. The new
condition set models how Firefox and Thunderbird decide compatibility to
smoothen future updates.
|
|
The git-makepkg-templates switched to dynamic adaptation to integrity
checks chosen in makepkg.conf. [1] The default checksums chosen reflect
recommendations from the Arch Linux Wiki and manual pages. [2]
[1]: https://github.com/dffischer/git-makepkg-templates/commit/e84d04b
[2]: https://aur.archlinux.org/cgit/aur.git/commit/?h=git-makepkg-templates-git&id=c2ccaaa
|
|
Theme and extension are currently published on addons.mozilla.org in
versions 45.1 and 42.1 respectively, indicating that a version
discrepancy is at least partially tolerable. So partially reverting
"version Firefox dependency" allows an intermixed installation of Git
and stable variants of the package.
|
|
They never existed in AUR4. Enough time has passed that any leftover
installation should be outdated and incompatible so that they are not
relevant for an update any longer.
This only affects relations to no longer preset packages, which will not
disturb existing installations, so they do not need to be triggered to
update with a pkgrel increment.
|
|
Despite the wild card * not coping hidden files, this does not exclude
such in subdirectories. A reliable method to exclude files by a pattern
like "starting with a dot" would be rsync. But to not pull it in as an
additional dependency, copy and find are preferred.
|
|
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.
|
|
The supported Firefox version rose to 45.
|
|
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.
|
|
As the pkgver function even runs before prepare, it is not possible to
move its contents down a directory level. Thus, the JSON description
should be found also when still in a subdirectory at this point of time.
|
|
This enables the package manager to detect a compatibility problem
between Firefox and the extension.
|
|
|
|
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.
This also enables one part of the split package to depend on other parts
from the same build or at least built from the same version, which
ensures compatibility.
|
|
Amongst other minor changes, this adds support for Firefox version 42.
|
|
As it is not used explicitly before being overwritten in, the first
assignment only reorders the .SRCINFO a little and can thus be removed.
|
|
The extension is used to configure the theme found in the same split
PKGBUILD, so both should come with the same version so to interact
properly.
|
|
This makes it easier to switch out the location this information is
retrieved from, should there be a more current source to query than the
install.rdf file included in the Add-On itself.
|
|
|
|
|