Custom shared directory between VM's

[lok...@gmail.com]

I regularly compile the latest version of Emacs for use in my development VM. I simply compile Emacs from the git repository and install it in /usr/local. All works the way it's supposed to.

However, I now have more than one VM where I need to use Emacs, and I would like to avoid having to compile it from source in both VM's.

The only way I can think of to handle this situation is to create a separate templatevm for this, enabline networking in the template so that I can use git from it, and then compile Emacs there.

Is there a better way to handle this? Ideally I'd like to be able to compile Emacs and install it to some specific directory that can then be made available to both VM's.

What is the best way to handle this situation?

[Unman]

That's a plausible approach.
I rarely enable further networking for templates- you can always git
clone in a disposableVM and them qvm-copy the directory in to the
template.

unman

[Ángel]

I would compile in a dev VM and create a "package" (which may be just a
tgz of /usr/local), then move it to the template VM.

Please note that on default templates, /usr/local is a symlink
to /rw/usrlocal (ie. it is per-VM), so you would want to make it a
normal folder before installing shared programs there.

Personally, I prefer having /usr/local at the template, and use
$HOME/bin for per-VM programs. Otherwise, there's no good place to
install a non-packaged program to several VMs.

Cheers