I wrote a git-multipkg command. It supports building arbitrary revisions of arbitrary branches of both local and remote git repositories. It doesn't support the --changelog or --mtime options of svn-multipkg, but otherwise works pretty well.
Since git doesn't have a notion of an incrementing revision number, the way p4 and svn do, I use the Unix timestamp of the revision being built as the package revision.
There are a couple of changes elsewhere in the code (e.g. to Multipkg.pm) that seemed necessary in order for multipkg to find all its various templates and scripts.
I wrote a git-multipkg command. It supports building arbitrary revisions of arbitrary branches of both local and remote git repositories. It doesn't support the --changelog or --mtime options of svn-multipkg, but otherwise works pretty well.
Since git doesn't have a notion of an incrementing revision number, the way p4 and svn do, I use the Unix timestamp of the revision being built as the package revision.
There are a couple of changes elsewhere in the code (e.g. to Multipkg.pm) that seemed necessary in order for multipkg to find all its various templates and scripts.