Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    CentOS 7/php56 dependencies

    Kopano Groupware Core
    3
    5
    642
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • pschoond
      pschoond last edited by

      I need to install Kopano on a existing server with php 5.6 from the IUS repositories ( https://ius.io/ ). Very stable for years and regularly updated. Much preferred by me over the Software Collections solution in this case.
      Been struggling last weeks with php-mapi having a different api version than php 5.6 but this seems ok on this installation, using the RHEL_7_PHP_56 repositories.

      The last dependency issue I’m running in to now is kopano-dagent being dependant on rh-php56-php from the Software Collections repo.

      I wonder if it would be possible to have this changed to a dependancy like php being >=5.6 so Kopano can also be installed using a different php repo ?

      Regards,
      Paul

      1 Reply Last reply Reply Quote 0
      • pschoond
        pschoond last edited by

        I can of course use --skip-broken but would rather not do this and I’m not sure if it would work.

        Paul

        umgfoin 1 Reply Last reply Reply Quote 0
        • umgfoin
          umgfoin @pschoond last edited by umgfoin

          It’s basically about php-mapi extension mapi.so.
          yum xxx --skip-broken won’t help, but
          rpm -Ivf --nodeps php-mapi-8.xxx.rpm probably does what you expect.

          Anyway, you have to move mapi.so / mapi.ini to the correct (IUS) php-locations.

          php-mapi-*.rpm installs this to scl-based paths e.g. under /opt/rh/rh-php56/root (./lib64/modules and ./etc).

          IMHO compiling Kopano from source is the better approach: You can hardcode your specific php-reincarnation during the configure-build-step

          The smime-plugin (if used) also depends on a custom php-extension (kopano_smime.so) which can be found (src) here.

          ++umgfoin

          fbartels 1 Reply Last reply Reply Quote 0
          • fbartels
            fbartels Kopano @umgfoin last edited by

            @umgfoin said in CentOS 7/php56 dependencies:

            IMHO compiling Kopano from source is the better approach: You can hardcode your specific php-reincarnation during the configure-build-step

            Yes, that is probably the better approach when using a php version we not specifically deliver ourselves.

            We actually hear complaints over the general scl architecture for red hat from now and then, but as of now this is the only way to go, if you still want to receive support from red hat.

            Regards Felix

            Resources:
            https://kopano.com/blog/how-to-get-kopano/
            https://documentation.kopano.io/
            https://kb.kopano.io/

            Support overview:
            https://kopano.com/support/

            1 Reply Last reply Reply Quote 0
            • pschoond
              pschoond last edited by

              @umgfoin For a production server I’d rather stay with repositories for maintainability, and since this is also about the supported Kopano version…

              @fbartels I get your point about using scl to garantee RedHat support. No easy escape than :-(

              1 Reply Last reply Reply Quote 0
              • First post
                Last post