summaryrefslogtreecommitdiff
path: root/dev-python/libvirt-python/libvirt-python-4.5.0.ebuild
diff options
context:
space:
mode:
authorMichal Privoznik <mprivozn@redhat.com>2019-03-17 06:50:06 +0100
committerMatthias Maier <tamiko@gentoo.org>2019-03-17 01:53:11 -0500
commit1a88084e8baffbe1b8fbe4d62c52ddc90d1a9e88 (patch)
tree4d24df5cc83bb7eaff5699ec1b77ef8f5a3b5a4b /dev-python/libvirt-python/libvirt-python-4.5.0.ebuild
parentb0c50b9cb54e16e7f2fae10c7a81ba19fc6cf0e2 (diff)
downloadgentoo-1a88084e8baffbe1b8fbe4d62c52ddc90d1a9e88.tar.gz
gentoo-1a88084e8baffbe1b8fbe4d62c52ddc90d1a9e88.tar.bz2
gentoo-1a88084e8baffbe1b8fbe4d62c52ddc90d1a9e88.zip
app-emulation/libvirt-9999: Update hash generation algorithm
I've noticed that bootstrap is run twice. This is because the first time it is run in src_prepare() and there some hash is computed so later when src_configre() gets its word it'll find everything prepared. Well, in the upstream commit of 6d53255377b50b7e412350d079 the hash was changed therefore src_configure() did not find the expected hash and thus re-ran the bootstrap script. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Matthias Maier <tamiko@gentoo.org>
Diffstat (limited to 'dev-python/libvirt-python/libvirt-python-4.5.0.ebuild')
0 files changed, 0 insertions, 0 deletions