So, anyone using OpenChange/SOGo is dependent on the Inverse Samba
packages for the foreseeable future?
It seems to me that places a lot of responsibility on Inverse for
maintaining not only SOGo packages but Samba, OpenChange and whatever
other packages become necessary. And, it ultimately limits user choices.
No more self-compiled installations; no more installations from
distro-provided packages, etc?
I am troubled by the possibility of having to purge my existing Samba
packages lest I *damage* my domain. I'll have a backup, so I can easily
restore my existing system, but the possibility of having to
re-provision remains.
Are there specific steps to backup the existing Samba DB? Can it be
exported/imported after-the-fact?
On 06/23/2015 11:27 AM, Ludovic Marcotte wrote:
On 23/06/2015 11:22, Rowland Penny wrote:
That is the very problem with Openchange, or it is as far as I am
concerned, you need to use the inverse samba packages or Openchange
will not work. In my opinion (for what it is worth) Openchange needs
to be a package that can be installed with *any* regular samba
packages, distro or Sernet, or a self compiled samba, it shouldn't
depend on samba being compiled in a certain way.
Indeed and that is why we provide the packages. It'll take *years*
before OpenChange is properly packaged on most distros. Some recent
distributions (like Jessie) have packages, but they are now old and
half-baked (no support for rpcproxy, for example).
--
Ludovic Marcotte
[email protected] :: +1.514.755.3630 ::http://inverse.ca
Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence
(http://packetfence.org)
--
[email protected]
https://inverse.ca/sogo/lists
