Based on discussion with @micharbet it looks that despite user guide and other guides the packages on CentOS/RHEL or dependencies for some role seems to slip out from radar of users when installing fast-vm which then leads to state that something doesn't work, or just prints warning and user may ignore it until it hits the real issue later.
Idea here is to have 2 fast-vm packages:
[x] fast-vm containing all "relevant" dependencies mentioned in user guide as required
[x] fast-vm-minimal containing minimal set of packages that can get fast-vm up and running without fatal crashes (in case that this would be considered for inclusion into any upstream distribution)
OndrejHome
commented
6 years ago
Based on discussion with @micharbet it looks that despite user guide and other guides the packages on CentOS/RHEL or dependencies for some role seems to slip out from radar of users when installing fast-vm which then leads to state that something doesn't work, or just prints warning and user may ignore it until it hits the real issue later.
Idea here is to have 2 fast-vm packages:
fast-vmcontaining all "relevant" dependencies mentioned in user guide as requiredfast-vm-minimalcontaining minimal set of packages that can get fast-vm up and running without fatal crashes (in case that this would be considered for inclusion into any upstream distribution)