Search Criteria
Package Details: birdtray-git latest-5
Package Actions
| Git Clone URL: | https://aur.archlinux.org/birdtray-git.git (read-only, click to copy) |
|---|---|
| Package Base: | birdtray-git |
| Description: | Run Thunderbird with a system tray icon. |
| Upstream URL: | https://github.com/gyunaev/birdtray |
| Keywords: | email notifier thunderbird tray |
| Licenses: | GPL-3.0 |
| Conflicts: | birdtray |
| Provides: | birdtray |
| Submitter: | jonathon |
| Maintainer: | yurikoles |
| Last Packager: | jonathon |
| Votes: | 5 |
| Popularity: | 0.000002 |
| First Submitted: | 2018-09-23 11:06 (UTC) |
| Last Updated: | 2020-04-23 17:01 (UTC) |
Dependencies (6)
- qt5-svg (qt5-svg-gitAUR)
- qt5-x11extras
- cmake (cmake3AUR, cmake-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- qt5-tools (make)
- qt5-translations (qt5-translations-gitAUR) (optional) – Support for translations
Latest Comments
jonathon commented on 2020-04-11 10:45 (UTC)
@dvalter Thank you, updated!
dvalter commented on 2020-04-11 10:16 (UTC) (edited on 2020-04-11 10:17 (UTC) by dvalter)
Thank you for PKGBUILD @jonathon.
Unfortunately there're some inaccuracies in dependency list.
Here's the patch suggestion:
jonathon commented on 2019-09-07 17:15 (UTC) (edited on 2019-09-07 19:56 (UTC) by jonathon)
I didn't actually forget anything, upstream changed their tagging structure and introduced a "RELEASE_" prefix with 1.6.
I've adjusted the
pkgverfunction accordingly.Edit:
@Kr1ss, ah that looks nicer than my quick change. I'll include that change next time I update the
PKGBUILD.Kr1ss commented on 2019-09-07 17:12 (UTC)
That's not really the case. The
$pkgvervariable is computed bymakepkgeverytime the package is build, by applying thepkgver()function. So what's in thePKGBUILDas a version does not really matter (except that it's probably no good style).The problem at the moment seems to be that upstream changed their tagging by prepending
RELEASE_to the version, which can easily be fixed in thePKGBUILDby changing thesedexpression inpkgver()to:vedg commented on 2019-09-07 17:00 (UTC)
@jonathon, you forgot to apply the pkgver variable part of Kr1ss's patch. Now the package is permanently out-of-date, i.e. "Version: latest (outdated installed version is RELEASE_1.6.r37.ge6cd346-1)". I think that the pkgver variable should be set to the actual latest git version of the package at the time of the last PKGBUILD change.
Kr1ss commented on 2018-10-12 16:01 (UTC)
Great ! Ty for the quick fix.
jonathon commented on 2018-10-12 15:26 (UTC)
Oops. That's what happens when I base the VCS package on the standard package rather than the other way round... :/
Fixed now.
Kr1ss commented on 2018-10-12 14:39 (UTC) (edited on 2018-10-12 14:46 (UTC) by Kr1ss)
Thx @jonathon, great package.
Sadly, the current
PKGBUILDjust labels each version "latest". So, despite of this being a VCS-package, thepkgverwon't be changed after an upstream commit and a rebuild, thus makepkg/pacman won't recognize that the package has actually changed.Would u mind adding a
pkgver()function to thePKGBUILD, e.g. something like :That would increase the version number with every commit, and append the hash ID of that commit.