Package Details: qtox-git 1.10.0.r0.g496f8548-1

Git Clone URL: https://aur.archlinux.org/qtox-git.git (read-only)
Package Base: qtox-git
Description: Powerful Tox client written in C++/Qt that follows the Tox design guidelines.
Upstream URL: https://github.com/qTox/qTox
Licenses: GPL3
Conflicts: qtox
Provides: qtox
Submitter: prurigro
Maintainer: DragonX256
Last Packager: DragonX256
Votes: 113
Popularity: 1.096631
First Submitted: 2014-07-13 08:46
Last Updated: 2017-05-08 04:19

Pinned Comments

DragonX256 commented on 2017-03-01 15:25

Well, I updated package by myself. And it compiles fine now.

Latest Comments

DragonX256 commented on 2017-03-01 15:25

Well, I updated package by myself. And it compiles fine now.

DragonX256 commented on 2017-02-21 13:49

Hey, @farseerfc! I've send a new PKGBUILD to you! Check your email!

DragonX256 commented on 2017-02-12 15:31

Hey, Maintainers! qTox can be built with CMake now! I think you need to update PKGBUILD.

farseerfc commented on 2017-01-07 21:13

To all, about current version, you may get a version like "1.7.0.r47.g5928413b" which seems out-of-date because "1.7.1" has been released. But if you look into git history you will find out that the tag "v1.7.1" is on a different path than the current master head. `git descibe` assigned the most recent *reachable* tag name as version name. There may be a git rebase occurred after the "v1.7.1" is tagged. So "1.7.0.r47.g5928413b" is acctually newer that "1.7.1".

farseerfc commented on 2016-12-21 15:43

@DragonX256 toxcore in community-testing has switched to c-toxcore upstream. Please wait for the stable release of qtox migrated to c-toxcore API. Sorry for the inconvenience.

DragonX256 commented on 2016-12-20 05:13

New commits using c-toxcore only, which should replace original toxcore in depends.

kubrick commented on 2016-05-14 12:45

> @kubrick actually the pkgver() is meaningful and does include the tag. it's `${latest_tag}.r${number_of_commits_since_tag}.g${commit_short_hash}`

I disagree, the pkgver is absolutely meaningless the way you kept on bumping it: it would only meaningful *if* there has not been any commit since the PKGBUILD was updated.
The only way of having the head of the master branch fetched (which is the point of a -git package) and have a meaningful pkgver is to use the pkgver function.

> Maybe a middle ground would be bumping this -git package only when there's a new tagged version

Yes, I fully agree. *but* you'd have to use pkgver to exactly fetch this tag.

farseerfc commented on 2016-05-13 12:26

@JZA where do you get tox-git? It's not in the AUR or official repositories. qtox-git depends on toxcore, so it cannot conflict with it.

JZA commented on 2016-05-13 10:12

this package conflict with toxcore:
==> Building and installing package
==> Install or build missing dependencies for qtox-git:
resolving dependencies...
looking for conflicting packages...
:: toxcore and tox-git are in conflict (tox). Remove tox-git? [y/N]

vith commented on 2016-05-03 16:25

I'm a bit late to the discussion about bumping the PKGBUILD on every commit/daily, but here are my thoughts:

# For
I appreciated automatically rebuilding on every git commit when I ran `pacaur -Syu`, if you don't want that, there's the non-git package that's only bumped for stable releases, or, you can add the git package to your ignored packages so you'll only see a warning about the new version being available but not automatically rebuild it. YMMV with other AUR helpers.

# Against
It's not what most AUR maintainers do so nobody's expecting it (clearly, from the other comments). I expect most AUR helper users won't be aware of the ignored packages feature available to them/all helpers might not have such a feature. Maybe a middle ground would be bumping this -git package only when there's a new tagged version.

Anyway, it didn't bother me, in fact it was convenient for me, but I'm not too bothered that it's gone either. I don't think it's too crazy of an idea. I had considered the possibility for other VCS AUR packages I maintain but just hadn't done it.

@kubrick actually the pkgver() is meaningful and does include the tag. it's `${latest_tag}.r${number_of_commits_since_tag}.g${commit_short_hash}`

All comments