On 14/03/12 01:49, Matthew Monaco wrote: > On 03/13/2012 06:15 AM, Allan McRae wrote: >> >> Hmm... good idea using the fragment identifier for specifying the >> branch/tag/commit to checkout. Being inspired by how pypi uses these to >> provide checksums, could I even suggest: >> >> <url>#branch=maint >> <url>#tag=v4.0.1 >> <url>#commit=f42ad345 >> >> This gives full clarity to what is being specified an allows for >> potential cases where branches and tags have the same name and we could >> provide multiple options, semicolon separated, if needed (obviously not >> for git, but maybe for another VSC system). >> > > That makes tag/commit unable to move forward automatically unless you can > always > specify a branch and then optionally a tag/commit. There are ways to get the > children of a commit though; makepkg could move to the tip of the branch if > there's only one child and complain if there's more. >
Everything there is optional. If you do not specify any of a branch/tag/commit, then makepkg would build from the head of the master branch. If you specify a branch, makepkg builds from the head of that branch. If you specify a commit/tag, makepkg builds from that commit/tag. Allan
