From: Adrian Bunk <bunk@stusta.de>
To: Andrej Valek <andrej.valek@siemens.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] squid: upgrade squid 3.5.28 -> 4.6
Date: Tue, 9 Apr 2019 13:05:04 +0300 [thread overview]
Message-ID: <20190409100504.GA12869@localhost> (raw)
In-Reply-To: <20190409084621.27294-1-andrej.valek@siemens.com>
On Tue, Apr 09, 2019 at 10:46:21AM +0200, Andrej Valek wrote:
>...
> - add openssl and esi as package options
>...
> -DEPENDS = "libtool krb5 openldap db cyrus-sasl openssl expat libxml2"
>...
> +DEPENDS = "libtool krb5 openldap db cyrus-sasl"
>
> inherit autotools pkgconfig useradd ptest perlnative
>
> @@ -51,6 +50,8 @@ PACKAGECONFIG[libnetfilter-conntrack] = "--with-netfilter-conntrack=${includedir
> PACKAGECONFIG[noatomics] = "squid_cv_gnu_atomics=no,squid_cv_gnu_atomics=yes,,"
> PACKAGECONFIG[ipv6] = "--enable-ipv6,--disable-ipv6,"
> PACKAGECONFIG[werror] = "--enable-strict-error-checking,--disable-strict-error-checking,"
> +PACKAGECONFIG[esi] = "--enable-esi,--disable-esi,expat libxml2"
> +PACKAGECONFIG[ssl] = "--with-openssl=yes,--with-openssl=no,openssl"
>...
It would be good to have such changes unrelated to the upgrade in a
separate commit.
Unless there's a reason to do otherwise, it would be better to have
these new options in the default PACKAGECONFIG so that a opt-out is
possible but the default doesn't change.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-04-09 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 8:46 [meta-networking][PATCH] squid: upgrade squid 3.5.28 -> 4.6 Andrej Valek
2019-04-09 8:55 ` Andrej Valek
2019-04-09 10:05 ` Adrian Bunk [this message]
2019-04-09 10:14 ` Andrej Valek
2019-04-10 12:02 ` Adrian Bunk
2019-04-10 12:24 ` Bach, Pascal
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=20190409100504.GA12869@localhost \
--to=bunk@stusta.de \
--cc=andrej.valek@siemens.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.