Package Details: cmst-git 2023.03.14-1

Git Clone URL: (read-only, click to copy)
Package Base: cmst-git
Description: QT GUI for Connman with system tray icon
Upstream URL:
Licenses: MIT
Conflicts: cmst
Provides: cmst
Submitter: whynothugo
Maintainer: pmattern
Last Packager: pmattern
Votes: 5
Popularity: 0.000010
First Submitted: 2014-07-07 00:02 (UTC)
Last Updated: 2023-04-30 14:36 (UTC)

Latest Comments

1 2 Next › Last »

xiota commented on 2023-04-09 08:02 (UTC)

Missing makedepends on qt5-tools.

neokuze commented on 2022-03-10 02:45 (UTC)


hagabaka commented on 2015-03-22 15:03 (UTC)

Most -git packages on AUR use whatever version is determined by pkgver() instead of "latest": This version is not always accurate of course, and either way makepkg will run pkgver() again to determine the current version. However the pkgver() value at the time of the last PKGBUILD update is still more useful information than "latest", because you know that the PKGBUILD should work for that commit/revision at least. So I don't think changing the wiki to suggest "latest" as a standard for VCS PKGBUILDs is a good idea.

whynothugo commented on 2015-03-22 08:35 (UTC)

@flamusdiu Nope, that change will never happen: a) Indeed, AUR helpers can't know if it's out-of-date or not because this tracks the latest git version. Until the latest HEAD is downloaded and pkgver() ran, there's no way to know if it's out of-date or not, hence, they'll report that an update is needed. Most packages won't actually re-build/package/compile if the pkgver has not increased. If your AUR helper does you should report the issue. b) There's no single value for pkgver. This PKGBUILD builds the latest for git. As soon as there's a commit upstream, the pkgver that this package builds has changed. There's not a change I'll keep re-uploading the package every time there's an upstream commit. c) Using "latest" is proper practice, since, again, this PKGBUILD does not target any specific version (and stating the contrary is merely wrong). I'll see if I can update the wiki with these details, so we can formally standardize these already common practices.

flamusdiu commented on 2015-03-22 02:12 (UTC)

@hobarrera: you need to update the pkgver in the PKGBUILD file. "latest" isn't the correct way to do this. Right, every time I run "aura -Au," It appears to be out-of-date. Usually, when building Git sourced PKGBUILDs, it will update the pkgver var properly. Just use that one to create the source tarball instead of leaving "latest."

whynothugo commented on 2015-01-25 18:35 (UTC)

@hagabaka No problem.

hagabaka commented on 2015-01-25 02:59 (UTC)

Sorry, I misclicked on flag-out-of-date.

hagabaka commented on 2015-01-20 17:16 (UTC)

The current PKGBUILD fails because debian/copyright is no longer in the respo. Here is a PKGBUILD that fixes that and a few formatting inconsistencies, as well as adds a pkgver() that follows the cmst package's version scheme:

AlfredoRamos commented on 2014-11-15 11:12 (UTC)

cmst-git E: Files in /usr/share/icons/hicolor but no call to gtk-update-icon-cache or xdg-icon-resource to update the icon cache cmst-git E: Missing custom license directory (usr/share/licenses/cmst-git) cmst-git E: Dependency hicolor-icon-theme detected and not included (needed for hicolor theme hierarchy)

sekret commented on 2014-08-01 19:15 (UTC)

No I meant if you checkout with https, that port should be open. You use git://[...], I suggest to use https://[...]. But to be fair, I don't know what's the default git port and if there's any difference.