[pacman-dev] The great VCS packages overhaul of 2015

Thomas Bächler thomas at archlinux.org
Tue Mar 13 06:25:06 EDT 2012

Am 13.03.2012 09:21, schrieb Allan McRae:
>> Is it at all feasible to just use the build date for package ordering if it's a
>> vcs package? This way the pkgver can be the ref that was checked out:
>>   - the short hash
>>   - the tag
>>   - the branch (_short hash maybe OR only automatically bump the pkgrel)
> I would really like to move away from the build date having anything to
> do with package ordering as it is entirely non-deterministic about what
> is in a package.

I cannot ACK that enough. Please, no build dates!

>>> source=(git://projects.archlinux.org/users/allan/pacman.git)
>>> _git_branch="working"
>>> _git_commit="8c857343"
>> Are these looking forward to other VCS's though? What scenario is more than one
>> ref needed? Makepkg would just be doing a checkout right?
> This might be me not understanding some of the subtleties of git, but
> this is what I see as options for building from a git repo...
> 1) build from master HEAD
> 2) build from a branch HEAD
> 3) build from a given commit/tag
> So, assuming that the git repo is checked out from upstream in $vcsdir,
> the command needed for each of these is:
> 1) git clone --branch master $vcsdir     [*]
> 2) git clone --branch <branch> $vcsdir
> 3) git clone $vcsdir; git checkout <ref>

You complicate things A LOT here. Specifying the branch and commit
separately is nonsense. The commit id already tells you exactly where
you want to be. This is the right thing to do:

$ git clone $vcsdir
$ git checkout -b makepkg $ref

Here, $ref can be a tag name, a branch name, a commit id or an
abbreviated commit id - everything git understands as a refspec. Let's
just give git a single refspec and let it handle the rest.

(I just realized I might be slightly wrong here, as we refer to branch
and tag names in a remote repository of a remote repository - but I am
sure some magic exists here that will make it just as easy as I
described, Dan probably knows.)

This is what you don't seem to understand: Once you have the commit id,
the branch name has no relevance anymore. You only need the branch name
when referencing the head of that branch.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/pacman-dev/attachments/20120313/4b4ab02d/attachment.asc>

More information about the pacman-dev mailing list