Arch Linux User Repository

Thanks for the reply. I've just noticed that the there's an offical pkgbuild-introspection package in the Arch's repo. Yaourt didn't show it as a proposal to installation. :/ It only showed the *-git package, so I thought that it's the only version available. :P

Well, m4 is part of base-devel. If you're building packages, you're required to have that installed. I don't know how you managed to find a carriage return in the source file -- it simply isn't there in the git repo.

I think this package needs a little more work. First I had to manually install the m4 package to make the build run and after that I've got: ==> Starting build()... GEN mkaurball mkaurball: line 5: syntax error near unexpected token `$'{\r'' 'kaurball: line 5: `array_build() { Makefile:22: recipe for target 'mkaurball' failed make: *** [mkaurball] Error 2

Could you fix the versioning now that the upstream repo has tags? It should be sufficient to use: git describe | sed 's/^v//;s/-/./g'

This package will soon be moved to [community]: https://mailman.archlinux.org/pipermail/aur-general/2014-May/028199.html This is so great! :)

I'm not interested in changing the name. Call it "room for expansion".

Also, @falconindy, what are your thoughts on renaming this package to 'mkaurball-git'? As stated in the README, end users should only be interested in mkaurball, so it makes sense to change the pkgname as such.

@falconindy, I just changed the pkgver to use the "0.0." style you described. I decided to not set epoch because this is a VCS package that probably very few people are using right now. Let me know if you want me to upload it again with 'epoch=1'.

This package currently serves almost no value, but I appreciate early adopters sending me bug reports *now* so that they can be discussed and addressed. You will NOT be able to use this to generate compliant .AURINFO files as they're supported today in the AUR. The longer term plan has been detailed on aur-dev with the lofty goal of leveraging .AURINFO to finally support split packages. If you haven't been following, I'd suggest referring to these 3 threads, in order: 1) https://mailman.archlinux.org/pipermail/aur-general/2014-January/026758.html 2) https://mailman.archlinux.org/pipermail/aur-dev/2014-January/002616.html 3) https://mailman.archlinux.org/pipermail/aur-dev/2014-January/002624.html @jstjohn: I'm not really interested in maintaining more than I need to, but I'm still mildly concerned that the pkgver here will not play nicely with future tagged versions. Previous PKGBUILDs I've written against untagged git repos usually prefix the version with "0.0." so that any future tags will hopefully sort before the first tag. See nghttp2-git for an example. I expect that the first tag of pkgbuild-introspection will be '1'.

I've found it useful, I was dumping the script to /usr/local/bin out of sheer laziness before you wrote this PKGBUILD. @andreyv: As far as I know, the AUR currently only supports the following .AURINFO declarations: https://mailman.archlinux.org/pipermail/aur-dev/2013-March/002428.html https://projects.archlinux.org/aur.git/commit/?id=5a1137363cb358593a64e0e6d0b0adeb1a9514ff I'm hoping that the recent surge of activity prompts more development on .AURINFO support, though I'm sure that patches would be welcomed if you want to help speed things up.