Package Details: aegisub-git 3.4.2.r98.17ea2947a-1

Git Clone URL: https://aur.archlinux.org/aegisub-git.git (read-only, click to copy)
Package Base: aegisub-git
Description: A general-purpose subtitle editor with ASS/SSA support
Upstream URL: http://www.aegisub.org
Licenses: BSD-3-Clause
Submitter: alucryd
Maintainer: arch1t3cht
Last Packager: arch1t3cht
Votes: 24
Popularity: 0.000000
First Submitted: 2012-08-27 19:37 (UTC)
Last Updated: 2025-05-22 14:00 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 13 Next › Last »

alucryd commented on 2013-12-05 19:25 (UTC)

It seems my deleting your last comment wasn't clear enough, so I'm gonna write it down so you can understand. Your comments are less than useless, please stop. And that also goes for dumb bug reports like the last one on our bug tracker. Now if you think upstream is always right about versioning, I feel for you, all the more for something that goes like 'version that has nothing to do with current repo commit-branch that nobody cares about-at least some relevant sum'. If you're using your own PKGBUILD, why the fuck do you even care? Sure, you nagging me has nothing to do with me... And yeah, I sure hope you have nothing more to say, because I don't really take kindly to people wasting my time and any more comment will simply be obliterated.

sl1pkn07 commented on 2013-12-05 17:02 (UTC)

"What useful information does your pkgver provide?" simple: use program naming for git releases (stable release use other version naming) "feel free to use stable aegisub or write your own PKGBUILD" since years ago "Or better yet, nag upstream so they use proper git tags instead of nagging me." this is applicable for you, no for me Greetings and finish discussion(?) PS: i see you don't like my gift :_(

alucryd commented on 2013-12-05 08:40 (UTC)

sl1pkn07: So what? What useful information does your pkgver provide? Only the last commit sum... Mine provides the latest stable aegisub version, the last commit number and the last commit sum. Now if you think this pkgver is a complete heresy, feel free to use stable aegisub or write your own PKGBUILD. Or better yet, nag upstream so they use proper git tags instead of nagging me.

sl1pkn07 commented on 2013-12-04 19:19 (UTC)

but your code invents a version that does not match real version of program program version: http://i.imgur.com/oC2RjY0.png your pkgver(): http://sl1pkn07.no-ip.com/paste/view/9198d094 my pkgver(): http://sl1pkn07.no-ip.com/paste/view/cff10786 6962 and 16cd907fe7482cb54a7374cd28b8501f138116be is a first commit/hash when move from SVN to GIT. version.sh use this for keep version naming greetings

alucryd commented on 2013-12-04 17:28 (UTC)

sl1pkn07: Look at your command from version.sh, then at mine, I think it's pretty clear why.

sl1pkn07 commented on 2013-12-04 14:13 (UTC)

https://github.com/Aegisub/Aegisub/blob/master/aegisub/build/version.sh then pkgver() { echo $(expr 6962 + $(git log --pretty=oneline 16cd907fe7482cb54a7374cd28b8501f138116be..HEAD 2>/dev/null | wc -l)).$(git symbolic-ref HEAD 2> /dev/null | sed 's|refs/heads/||g').$(git rev-parse --short HEAD) } greetings

sl1pkn07 commented on 2013-12-04 14:00 (UTC)

@Alucryd why no use pkgver() with program version naming? http://i.imgur.com/oC2RjY0.png greetings

alucryd commented on 2013-09-15 22:38 (UTC)

Corubba: I know, I'm the one who updated it.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 13 Next › Last »