summaryrefslogtreecommitdiff
path: root/pcr/timekpr
diff options
context:
space:
mode:
authorbill-auger <mr.j.spam.me@gmail.com>2020-10-17 18:36:11 -0400
committerbill-auger <mr.j.spam.me@gmail.com>2020-10-21 23:11:11 -0400
commit96904734e943290416b016076b107bf46540ebe7 (patch)
treea1caef08afb40fccb5a3f66bfba1a454b75ad697 /pcr/timekpr
parentfcbc7ad6e43184a907f0db1ca235ea92cff4b0bf (diff)
downloadabslibre-96904734e943290416b016076b107bf46540ebe7.tar.gz
abslibre-96904734e943290416b016076b107bf46540ebe7.tar.bz2
abslibre-96904734e943290416b016076b107bf46540ebe7.zip
[virt-manager]: package 'virt-manager'
the changes in this patch are more extensive than what the commit message would suggest they are predominantly for the sake of minimizing the diff with upstream this is a split package upstream; but only 'virt-install' is on the blacklist originally, the package_virt-manager() function was deleted and the package_virt-install() function was left in tact, including the code that splits the output files into two packages that made this PKGBUILD quite confusing: * the pkgbase and abslibre directory are named 'virt-manager' * the PKGBUILD is still formatted as a split package, which happens to output only one single package * some non-package files are stashed aside, for apparently no reason, rather than making the intention obvious by deleting them all of the work necessary to output the 'virt-manager' package, is necessarily done by this PKGBUILD while building 'virt-install' (the package_virt-manager() function is merely a `mv` statement); so there is no reason not to package both packaging 'virt-manager' also has the benefit, of the pinned 'virt-install' dependency of 'virt-manager', being always satisfiable been added to the blacklist with reason: 'technical' virt-manager has been added to the blacklist with reason: 'technical'
Diffstat (limited to 'pcr/timekpr')
0 files changed, 0 insertions, 0 deletions