Package Details: talkingarch-git 0.0-1

Git Clone URL: (read-only, click to copy)
Package Base: talkingarch-git
Description: Builds TalkingArch, an unofficial Arch Linux live CD with speech and braille support added
Upstream URL:
Licenses: GPL
Conflicts: talkingarch
Provides: talkingarch
Submitter: None
Maintainer: lilmike
Last Packager: kyle
Votes: 5
Popularity: 0.000000
First Submitted: 2010-03-22 16:07
Last Updated: 2019-01-31 13:45

Dependencies (4)

Required by (0)

Sources (1)

Latest Comments

krprescott commented on 2015-07-20 04:00

This is just to import to the new AUR.

krprescott commented on 2015-05-03 04:41

Just updated package to reflect the new GIT repository.

kyle commented on 2015-05-02 10:44

I just caught my mistake in the previous comment. The source shouldn't look like
Instead, it should look like
Sorry for the typo.

kyle commented on 2015-04-22 17:26

I just heard the sound of the death knell for Gitorious once again, this time via the AUR e-mail list, immediately prior to writing this comment. As I have officially migrated the TalkingArch git repository to
I am already no longer pushing updates to the repository at Gitorious, which will become incapable of receiving updates no later than the middle of next month anyway. Please change the git source in this PKGBUILD from




at your earliest convenience, as I will need this change made before I can release the next TalkingArch iso, which is due out as close to the first of May as the official Archiso snapshot will allow. Thanks much.

kyle commented on 2014-02-10 00:10

Well, I originally commented that the pkgver variable could be set at 0.0 because of the pkgver() function, but the archiso-git PKGBuild has a version set and also has a working pkgver() function, so it looks like all bets are off. I probably should tag the release snapshots in the git repo anyway, to make them easier to track.

kyle commented on 2014-02-10 00:01

Because this is a git package, the pkgver variable can be set at 0.0. There is a pkgver() function below the normal fields that, once uncommented, will fully automate the process of setting the package version to the latest git commit. The only other thing that may need to be done is for each release to be tagged in the git repo, so that a release will get a version number that corresponds to the release date, but that shouldn't change the way the pkgver() function works.

krprescott commented on 2014-02-09 05:32

No changes, just updated version to be consistant with the most recent release