Virtual Machine manager?
Virtual Machine manager?
Is there a way to install Virtual Machine manager, I can't see it listed in the available packages. Do I need to add another source Repository for it to be found.
Re: Virtual Machine manager?
Try looking in Sourcery - be sure to check dependencies (when you click to tick the box, select "Get info" rather than install).
Adding source repositories should be done with caution if at all.
Adding source repositories should be done with caution if at all.
Re: Virtual Machine manager?
If you mean something like a frontend to run qemu VMs, try aqemu. You'll find it in sourcery/slapt-src.
Re: Virtual Machine manager?
I understand there is a new version of virt-manager available but how do I install this? virt-manager is not available from Gslapt package manager. How do I also ensure that I have the latest versions of all dependent packages. Is there a seperate repository I should be adding or something like that.
Thanks,
Thanks,
Re: Virtual Machine manager?
How did you install the older version?NickC wrote:I understand there is a new version of virt-manager available but how do I install this?
No. If you want to have the latest version of everything installed and being served to you in a plate, you're using the wrong distribution.NickC wrote:How do I also ensure that I have the latest versions of all dependent packages. Is there a seperate repository I should be adding or something like that.
Re: Virtual Machine manager?
Your best bet may be to use an alternative, but failing that, you'll need to compile from source.
As I said above, adding repos to the package manager is a bad idea unless you know what you're doing. The problem is that it's highly likely that something in the repo will break your installation. The whole point of a repo is that it's a consistent set of packages that have been tested on the distro. As a way of getting extra software, adding a repo isn't so much cracking a nut with a sledgehammer as (potentially and probably) a bull in a china shop.
If you do want to try compiling from source, there may be people on this forum who can help with any problems you encounter. But using an alternative is definitely the easier option. Have a look around to see what's there
EDIT
Do you mean this package from slapt-src / Sourcery?
if so installation using Sourcery is relatively easy though it can be a bit laborious if there are a lot of dependencies. Just make sure you have the deps installed first, in the order they are listed.
As I said above, adding repos to the package manager is a bad idea unless you know what you're doing. The problem is that it's highly likely that something in the repo will break your installation. The whole point of a repo is that it's a consistent set of packages that have been tested on the distro. As a way of getting extra software, adding a repo isn't so much cracking a nut with a sledgehammer as (potentially and probably) a bull in a china shop.
If you do want to try compiling from source, there may be people on this forum who can help with any problems you encounter. But using an alternative is definitely the easier option. Have a look around to see what's there

EDIT
Do you mean this package from slapt-src / Sourcery?
Code: Select all
root[vanilla]# slapt-src --search virt-manager
virt-manager:0.9.0 - virt-manager (a gtk interface for libvirt)
Re: Virtual Machine manager?
Yes that is one of them. virt-manager is not listed in Gslapt but version 0.9.0 is available in sourcery.
There is also virt-manager 0.9.1 released 31 Jan 2012 - I found that one earlier in a Slackware repository somewhere but can locate it at the moment. Question is if I go with the latest virt-manager 0.9.1, should I also ensure that all of its dependents are upgraded to the latest versions as well.
There is also virt-manager 0.9.1 released 31 Jan 2012 - I found that one earlier in a Slackware repository somewhere but can locate it at the moment. Question is if I go with the latest virt-manager 0.9.1, should I also ensure that all of its dependents are upgraded to the latest versions as well.
Re: Virtual Machine manager?
Wherever you get it from, there should be a README or INSTALL file that gives information on dependencies, specifying the minimum version if that's critical. In any case, if it does turn out you need newer versions than those you have, the build will fail, and the last few lines of output should indicate what made it fail.
However, reading your post more closely, it seems as though you have found a *package*, in which case I suppose you could try first installing all the deps mentioned in the slackbuild for the older version available through sourcery, in order, starting with libvirt I think (some may be available through Gslapt / slapt-get, not necessarily the same version); then manually install the package you downloaded and see whether it works. It would be worth looking on the virt-manager website for info about minumum version requirements for the deps; you may need to download the source to see this information.
In a word, a bit of trial and error are needed (and unless 9.1 has significant advantages over 9.0, it may not be worth the trouble). Good luck!
However, reading your post more closely, it seems as though you have found a *package*, in which case I suppose you could try first installing all the deps mentioned in the slackbuild for the older version available through sourcery, in order, starting with libvirt I think (some may be available through Gslapt / slapt-get, not necessarily the same version); then manually install the package you downloaded and see whether it works. It would be worth looking on the virt-manager website for info about minumum version requirements for the deps; you may need to download the source to see this information.
In a word, a bit of trial and error are needed (and unless 9.1 has significant advantages over 9.0, it may not be worth the trouble). Good luck!
