Package Details: git-town 14.2.2-1

Git Clone URL: https://aur.archlinux.org/git-town.git (read-only, click to copy)
Package Base: git-town
Description: Generic, high-level Git workflow support
Upstream URL: https://github.com/git-town/git-town
Licenses: MIT
Submitter: allonsy
Maintainer: alerque
Last Packager: alerque
Votes: 9
Popularity: 0.000000
First Submitted: 2015-08-01 05:10 (UTC)
Last Updated: 2024-06-06 23:46 (UTC)

Latest Comments

1 2 3 Next › Last »

alerque commented on 2022-01-20 19:10 (UTC) (edited on 2022-01-20 19:14 (UTC) by alerque)

@allonsy

Re requiring go toolchain: yes absolutely we want to require go to build this. In fact according to the Arch AUR guidelines it is required to build from sources when sources are available. If people are too lazy to build they can use the -bin package variant instead (or build in a chroot so they don't have to pollute their host system, or use my user repo)

Re adoption without your consent: this package had been flagged OOD since last June or something like that. When you file an orphan request for a package that has been manually flagged for a long time (90 days I think) the request is automatically approved. Ones that haven't been flagged for so long require a 14 day wait period and a manual approval by a TU. I filled an orphan request because this was 6+ months out of date and it was instantly orphaned, so I adopted it. Also note I reposted the upstream binary variant you had here and already orphaned it, if you want to continue that feel free to adopt.

allonsy commented on 2022-01-19 18:44 (UTC)

As a question (just curious, not a negative reflection at all), how were you able to adopt the package without my consent? Was it because I haven't updated the package in a while the system marked the package as orphaned? I could also just be mis-understanding the AUR package ownership system.

With that being said, I'm happy if you want to maintain this I'm just curious about the procedure there.

allonsy commented on 2022-01-19 18:41 (UTC)

Do we really want users to have to pull in the entire go toolchain just to build this small package?

It seems a bit overkill, right?

alerque commented on 2022-01-19 10:17 (UTC)

This PKGBUILD now builds from sources.

alerque commented on 2022-01-19 09:19 (UTC) (edited on 2022-01-19 10:17 (UTC) by alerque)

This package has, till now, been incorrectly named. According to the packaging guidelines any package where the source is available but installation is from an upstream provided binary must be named -bin. I'm reposting the history of this repo as git-town-bin and (having just adopted this) plan to overhaul this package to build from sources. I am not really interested in the binary package and will probably orphan it after posting. Expect the next updates to this to build from sources.

allonsy commented on 2020-09-23 21:40 (UTC)

Now changed to use new org URL and bumped the version

allonsy commented on 2019-06-07 00:09 (UTC)

Bumped to v7.2.1

allonsy commented on 2018-06-17 02:48 (UTC)

Bumped to 7.2.0

allonsy commented on 2018-04-25 22:49 (UTC)

bumped to 7.1.1

allonsy commented on 2018-02-03 22:27 (UTC)

bumped to 6.0.1