1 Topic by rafaelpossa

  • rafaelpossa
  • Member
  • Offline
  • Registered: 2014-03-15
  • Posts: 7

Topic: Package maintenance on FreeBSD 10.1-RELEASE-p9

I usually use pkg to install any packages on my FreeBSD box, but the iRedmail install scripts compiled from source using what I am assuming is ports.

In a fresh freebsd install, after installing iRedmail, I have the following output of 'pkg upgrade':

# pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (160 candidates): 100%
Processing candidates (160 candidates): 100%
The following 35 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        php56-session: 5.6.8
        php56: 5.6.8
        php56-xml: 5.6.8
        php56-dom: 5.6.8
        php56-filter: 5.6.8
        php56-json: 5.6.8
        php56-pdo_mysql: 5.6.8
        php56-pdo: 5.6.8
        php56-mysql: 5.6.8
        php56-mbstring: 5.6.8
        php56-iconv: 5.6.8
        php56-zip: 5.6.8
        libzip: 0.11.2_2

Installed packages to be REINSTALLED:
        roundcube-1.1.1,1 (options changed)
        py27-MySQLdb-1.2.5 (options changed)
        py27-Jinja2-2.7.3 (options changed)
        postfix-2.11.4,1 (options changed)
        policyd2-2.0.14 (direct dependency changed: php56)
        php55-5.5.24 (options changed)
        pecl-intl-3.0.0_2 (direct dependency changed: php56)
        p5-Net-DNS-0.83_1 (options changed)
        p5-IO-Socket-SSL-2.012 (options changed)
        mod_php55-5.5.24 (options changed)
        m4-1.4.17_1,1 (options changed)
        libiconv-1.14_8 (options changed)
        gnupg1-1.4.19 (needed shared library changed)
        dovecot2-2.2.16_1 (options changed)
        dialog4ports-0.1.5_2 (option removed: GNUTLS)
        cyrus-sasl-2.1.26_9 (options changed)
        curl-7.42.1 (options changed)
        cmake-3.1.3 (options changed)
        ca_root_nss-3.18.1 (options changed)
        apr-1.5.1.1.5.4 (options changed)
        apache24-2.4.12 (options changed)
        amavisd-new-2.10.1_1,1 (options changed)

The process will require 19 MiB more space.
26 MiB to be downloaded.

Should I lock these packages to not  be changed/upgraded or would it be okay to let pkg make changes?


Thanks,
Rafael




==== Required information ====
- iRedMail version: 0.9.0
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Linux/BSD distribution name and version: FreeBSD 10.1-RELEASE-p9
- Related log if you're reporting an issue:
====

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,768

Re: Package maintenance on FreeBSD 10.1-RELEASE-p9

The difference between binary packages and installing with ports tree is, different compile options.
For example, you may want Dovecot to support MySQL query, this way you need to enable mysql support while compiling Dovecot.

How do you solve this with binary package?

3 Reply by rafaelpossa (edited by rafaelpossa 2015-05-12 08:30:40)

  • rafaelpossa
  • Member
  • Offline
  • Registered: 2014-03-15
  • Posts: 7

Re: Package maintenance on FreeBSD 10.1-RELEASE-p9

Hello,

Thanks for your response.

I understand that in order to compile software with additional options, you have to use ports. My original question was if I should use the lock function of "pkg" so that it doesn't attempt to change the packages that were installed by iRedmail. Does that make sense to you? It's just an idea that I have, but I am wondering if you have any other suggestions!

Thanks again,
Rafael

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,768

Re: Package maintenance on FreeBSD 10.1-RELEASE-p9

rafaelpossa wrote:

My original question was if I should use the lock function of "pkg" so that it doesn't attempt to change the packages that were installed by iRedmail.

Should be fine. But if you want to upgrade packages, why not use tools like 'portmaster'?

5 Reply by rafaelpossa

  • rafaelpossa
  • Member
  • Offline
  • Registered: 2014-03-15
  • Posts: 7

Re: Package maintenance on FreeBSD 10.1-RELEASE-p9

Sounds good. Is it okay to upgrade the packages before an upgrade of iRedmail comes out? Since it's a production server I am afraid that upgrading any of the packages may cause the installation to break.

6 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,768

Re: Package maintenance on FreeBSD 10.1-RELEASE-p9

rafaelpossa wrote:

Is it okay to upgrade the packages before an upgrade of iRedmail comes out? Since it's a production server I am afraid that upgrading any of the packages may cause the installation to break.

Should be fine.

7 Reply by rafaelpossa

  • rafaelpossa
  • Member
  • Offline
  • Registered: 2014-03-15
  • Posts: 7

Re: Package maintenance on FreeBSD 10.1-RELEASE-p9

Thank you.

ZhangHuangbin wrote:
rafaelpossa wrote:

Is it okay to upgrade the packages before an upgrade of iRedmail comes out? Since it's a production server I am afraid that upgrading any of the packages may cause the installation to break.

Should be fine.