From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/dovecot: New package
Date: Mon, 29 Sep 2014 19:13:14 +0200 [thread overview]
Message-ID: <20140929191314.36b87a70@free-electrons.com> (raw)
In-Reply-To: <1411925137-11284-1-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Sun, 28 Sep 2014 19:25:36 +0200, Bernd Kuhls wrote:
> +DOVECOT_VERSION_MAJOR = 2.2
> +DOVECOT_VERSION = $(DOVECOT_VERSION_MAJOR).13
> +DOVECOT_SITE = http://www.dovecot.org/releases/$(DOVECOT_VERSION_MAJOR)
> +DOVECOT_INSTALL_STAGING = YES
> +DOVECOT_LICENSE = LGPLv2.1; some exceptions are mentioned in COPYING
I think we generally say only "<foo> with exceptions".
Did you check that it's LGPLv2.1 vs. LGPLv2.1+ ?
> +DOVECOT_LICENSE_FILES = COPYING COPYING.LGPL COPYING.MIT
> +DOVECOT_DEPENDENCIES = host-pkgconf openssl zlib $(if $(BR2_PACKAGE_LIBICONV),libiconv)
If you do this with libiconv, then don't you need:
select BR2_PACKAGE_LIBICONV if !BR2_ENABLE_LOCALE
libiconv is a replacement for the missing iconv stuff in libc when
locale support is not enabled.
If zlib is really a mandatory dependency, then it should be selected
from the Config.in file.
> +DOVECOT_CONF_OPT = \
> + --with-dovecot=/usr/lib \
> + --without-dovecot-install-dirs \
> + --libexecdir=/usr/bin/dovecot \
This looks weird. You really want /usr/bin/dovecot as a lib directory?
Shouldn't this be /usr/lib/dovecot instead?
> + --with-moduledir=/usr/lib \
> + --sysconfdir=/etc \
> + --localstatedir=/var \
> + --without-sql \
> + --with-zlib \
Optional dependency?
> + --with-ssl=openssl \
Ditto?
> + --without-docs
> +
> +ifeq ($(BR2_PACKAGE_BZIP2),y)
> +DOVECOT_CONF_OPT += --with-bzlib
> +DOVECOT_DEPENDENCIES += bzip2
> +else
> +DOVECOT_CONF_OPT += --without-bzlib
> +endif
> +
> +ifeq ($(BR2_PACKAGE_LIBCAP),y)
> +DOVECOT_CONF_OPT += --with-libcap
> +DOVECOT_DEPENDENCIES += libcap
> +else
> +DOVECOT_CONF_OPT += --without-libcap
> +endif
> +
> +define DOVECOT_POST_CONFIGURE
> + for i in $$(find $(@D) -name "Makefile"); do \
> + $(SED) 's%^pkglibdir =.*%pkglibdir = \$$(libdir)%' $$i; \
> + $(SED) 's%^pkglibexecdir =.*%pkglibexecdir = \$$(libexecdir)%' $$i; \
> + done
> +endef
> +
> +DOVECOT_POST_CONFIGURE_HOOKS += DOVECOT_POST_CONFIGURE
> +
> +define DOVECOT_FIX_STAGING_DOVECOT_CONFIG
> + $(SED) 's,^LIBDOVECOT_INCLUDE=.*$$,LIBDOVECOT_INCLUDE=\"-I$(STAGING_DIR)/usr/include/dovecot\",' $(STAGING_DIR)/usr/lib/dovecot-config
> + $(SED) 's,^dovecot_pkglibexecdir=.*$$,dovecot_pkglibexecdir=/usr/bin,' $(STAGING_DIR)/usr/lib/dovecot-config
> +endef
dovecot-config is in $(STAGING_DIR)/usr/lib ? This looks weird.
> +
> +DOVECOT_POST_INSTALL_STAGING_HOOKS += DOVECOT_FIX_STAGING_DOVECOT_CONFIG
> +
> +$(eval $(autotools-package))
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-29 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 17:25 [Buildroot] [PATCH 1/2] package/dovecot: New package Bernd Kuhls
2014-09-28 17:25 ` [Buildroot] [PATCH 2/2] package/dovecot-pigeonhole: " Bernd Kuhls
2014-09-29 17:14 ` Thomas Petazzoni
2014-09-29 17:13 ` Thomas Petazzoni [this message]
2014-10-03 9:33 ` [Buildroot] [PATCH 1/2] package/dovecot: " Bernd Kuhls
2014-10-03 11:40 ` Thomas Petazzoni
2014-10-03 12:32 ` Bernd Kuhls
2014-10-03 14:12 ` Bernd Kuhls
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140929191314.36b87a70@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox