call it the same as the kernel, i.e., pve- prefix not pmg-,
as the kernel is also prefixed with pve- on PMG..
Not to nice but better than now starting to mix this up and cause
even more confusion...
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
If PMG gets installed in a container environment, e.g., in PVE CTs,
the installation does not requires its own kernel, as the host kernel
is used anyway. So add a new separate meta package which can be used
to install, or to switch, to such a setup.
A user can save well a third of the additional space required on top
of a quite minimal Debian installation, i.e., proxmox-mailgateway:
> 0 upgraded, 183 newly installed, 0 to remove and 0 not upgraded.
> Need to get 153 MB of archives.
> After this operation, 638 MB of additional disk space will be used.
vs. with new proxmox-mailgateway-container:
> 0 upgraded, 169 newly installed, 0 to remove and 0 not upgraded.
> Need to get 59.9 MB of archives.
> After this operation, 206 MB of additional disk space will be used.
This quite big difference does not comes only from the kernel, but
also it's dependencies like grub, initramfs-tools, pve-firmware, ...
On new CT installations you can just setup the PMG by installing:
> apt install proxmox-mailgateway-container
and be done, if you need to switch to a system with kernel you can do
so by installing proxmox-mailgateway .
To make a switch on an existing system you need to do the following:
> apt install proxmox-mailgateway-container
> apt purge pve-kernel-*
> apt autoremove --purge
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
