FS#48249 - [virt-install] pkgbase use creates avoidable dependency issues
Attached to Project:
Community Packages
Opened by deusstultus (deusstultus) - Friday, 19 February 2016, 09:33 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 10 March 2016, 17:49 GMT
Opened by deusstultus (deusstultus) - Friday, 19 February 2016, 09:33 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 10 March 2016, 17:49 GMT
|
Details
Description:
If virt-install is installed without virt-manager, the virt-manager script is still in $PATH and results in errors when running virt-manager if the dependencies are not installed. Usually this is handled with optdepends, but that would create an Ouroboros here. I like the idea of splitting these to allow headless creation without the bloat, but it's sloppy at present. I've pushed a couple PKGBUILD implementations to https://gist.github.com/deusstultus/2e0be0f219d9576f1ace which seek to resolve the issue in a couple ways. simple.PKGBUILD is a quick patch to only remove the link from /usr/bin without detailed testing, while PKGBUILD sought to begin a route to better map the files to the appropriate packages. namcap also barks heavily based on dependency use as expected per above. Additional info: pkgver=1.3.2 pkgrel=2 Steps to reproduce: ``` $ pacman -S virt-install #on clean root $ which virt-manager /usr/bin/virt-manager $ virt-manager <Dependency conflicts arise> ``` |
This task depends upon