Package Details: doomretro-git 5.2.1.r183.g366d50525-1

Git Clone URL: https://aur.archlinux.org/doomretro-git.git (read-only, click to copy)
Package Base: doomretro-git
Description: The classic, refined DOOM source port (git version)
Upstream URL: http://doomretro.com
Licenses: GPL3
Conflicts: doomretro
Provides: doomretro
Submitter: Kaan
Maintainer: FredBezies
Last Packager: FredBezies
Votes: 2
Popularity: 0.000017
First Submitted: 2017-06-20 08:18 (UTC)
Last Updated: 2024-02-25 12:06 (UTC)

Dependencies (5)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

xDShot commented on 2020-06-27 09:40 (UTC)

Shouldn't it pull latest commit instead?

FredBezies commented on 2020-06-27 09:24 (UTC)

Erh...

https://github.com/bradharding/doomretro/releases/tag/v3.5.10

"DOOM Retro v3.5.10

@bradharding bradharding released this 20 days ago · 111 commits to master since this release"

xDShot commented on 2020-06-27 08:38 (UTC)

Weird. Currently latest commit is fa29145e173e1db96bf4532475c4ed19f61df0fc but package version is 3.5.10.r111.gfa29145e1-1

FredBezies commented on 2020-06-27 05:50 (UTC)

@xDShot: worked for me this morning. Just try again :)

xDShot commented on 2020-06-27 02:52 (UTC)

Doesn't clone with latest pushed upstream commit, it appears.

FredBezies commented on 2020-06-08 10:26 (UTC)

@grawlison: So let's follow the holy scriptures... Erh, I mean Arch wiki and some people will think: this package is too old, I have to push an orphan request.

How many messages every month on aur mailing list are related to old vcs PKGBUILD?

I manage this pkgbuild to show everyone it is alive. I don't walk on your feet outdating your doomretro stable pkgbuild.

So let me alone. Thanks.

grawlinson commented on 2020-06-08 10:10 (UTC)

Suffix pkgname with -cvs, -svn, -hg, -darcs, -bzr, -git etc. unless the package fetches a specific release. If the resulting package is different after changing the dependencies, URL, sources, etc. increasing the pkgrel is mandatory. Touching the pkgver is not.

From VCS package guidelines. You should only be uploading to the AUR if the PKGBUILD requires new or updated build steps.

FredBezies commented on 2020-05-30 09:13 (UTC)

I know this. I will stay with point release now. I think you'll be happy!

grawlinson commented on 2020-05-30 09:12 (UTC)

But you don’t need to push an update, that’s the whole point of VCS packages.

FredBezies commented on 2020-05-30 08:57 (UTC)

@grawlison: I know, but when I push an update, it builds.