On Sat, Feb 21, 2015 at 09:18:08AM +0100, Michał Górny wrote: > neovim: > > > # Copyright 1999-2015 Gentoo Foundation > > # Distributed under the terms of the GNU General Public License v2 > > # $Header: $ > > > > EAPI=5 > > inherit cmake-utils flag-o-matic > > > > DESCRIPTION="Vim's rebirth for the 21st century" > > HOMEPAGE="https://github.com/neovim/neovim"; > > if [[ ${PV} == 9999 ]]; then > > inherit git-r3 > > EGIT_REPO_URI="git://github.com/neovim/neovim.git" > > KEYWORDS="" > > else > > inherit vcs-snapshot > > COMMIT="8efb3607a7f6cefce450953c7f8d5e3299347bae" > > SRC_URI="https://github.com/${PN}/${PN}/tarball/${COMMIT} -> > > ${P}.tar.gz" > > I don't think relying on stability of generated tarballs is a good > idea. The same applies to almost all other ebuilds.
If the tarball is based on an upstream tag, you should be fine, but this does not work for a commit hash like what is being used here. For more info on this, check out the man page for git archive. In particular, how it handles timestamps inside the tarball. In a nutshell, if you use git archive to create a tarball based on a commit hash, the time stamps of the files inside the tarball are different each time you create it, but this is not true if the tarball is based on an upstream tag. William
signature.asc
Description: Digital signature
