Arch Linux

logfiles are already shown for both -d and -l.

-v -> patch welcome.

Quick aif version patch.
adds -v and echos "aif$PKGVER-$PKGREL"

If you want me to patch it a different way then please let me know. (maybe PKGBUILD updating it)

Well this is embarrassing. I forgot to end the v case with ;;.

Updated patch added.

Final version, I promise.

added an exit after we print the version. (duh)

we need something that will automatically tell us the correct git tag (or git commit hash, if there is no git tag).
maybe we can do this with make.

it should also be distro-agnostic (no package revisions)

I forgot about this bug! XD
will post back with ideas :P

how about using something like
git describe --tags

we could also use
git rev-parse HEAD

Which will just show the git commit hash, the previous command (git describe --tags) should probably be used though.

Any thoughts?

would this be good?

something like this yes, but some remarks:
- maybe we should instead of:
echo "aif $VERSION"
do:
if [ -z "$VERSION" ] ; echo 'unknown version'; else echo "aif $VERSION"; fi
or something
- i don't really understand what the '--tags' does (ie what lightweight (non-annotated) tag are). they definitely look weird (a tag + part of a commit hash?)

ideally i want this:
* if source tree corresponds to a tag, use tag
* if it doesn't, use the commit hash
and this should work both in a git checkout or in a tarball (that has no .git folder).
for uzbl we already do most of this http://github.com/Dieterbe/uzbl/blob/master/misc/hash.sh, just not the "fallback on commit hash if there it's not a tag"

speaking with the people at #git it seems that the repo doesn't use annotated tags.

"me: so I did git checkout tagname and when I ran git describe --exact-match HEAD I get fatal: no tag exactly matches
pantsman: it seems to only work for annotated tags
pantsman: I don't know if that's intended or a bug
pantsman: I always found it odd
pantsman: I believe it's preferable to use annotated tags anyway"

It seems what you're looking for is git describe --exact-match HEAD (same as git describe?) but to use it the repo needs to start using annotated tags (git tag -a tagname), otherwise I think the only way would be to use git describe --tags.

decision?