From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] php: bump version to 7.0.5
Date: Thu, 14 Apr 2016 11:12:36 -0300 [thread overview]
Message-ID: <570FA554.1090503@zacarias.com.ar> (raw)
In-Reply-To: <1460629691-56260-1-git-send-email-Vincent.Riera@imgtec.com>
On 14/04/16 07:28, Vicente Olivert Riera wrote:
> - php-geoip: switched to HEAD of master on GitHub.
> - Bug: https://bugs.php.net/bug.php?id=71083
>
> - php-gnupg: switched to HEAD of master on GitHub.
> - Bug: https://bugs.php.net/bug.php?id=71138
>
> - php-imagick: bump version to 3.4.1.
> - Necessary to work with php-7.
>
> - php-memcached: switched to HEAD of master on GitHub.
> - Bug: https://bugs.php.net/bug.php?id=70751
>
> - php-ssh2: switched to HEAD of master on GitHub.
> - Bug: https://bugs.php.net/bug.php?id=71376
>
> - php-yaml: bump version to 2.0.0RC7.
> - Necessary to work with php-7.
>
> - php-zmq: bump version to 1.1.3.
> - Necessary to work with php-7.
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Hi Vicente.
I believe splitting the pecl package bumps in a first batch of patches
with the php bump at the end would be better suited, as long as those
packages can built against the current php (normally they should).
This would result in better bisectability, and no "all these bumps fix
the build failures" scenario leading the php bump.
Some people might argue about having both php versions side by side but
i'm not one of them if we can avoid it.
Regards.
next prev parent reply other threads:[~2016-04-14 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 10:28 [Buildroot] [PATCH] php: bump version to 7.0.5 Vicente Olivert Riera
2016-04-14 14:12 ` Gustavo Zacarias [this message]
2016-04-14 15:39 ` Vicente Olivert Riera
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=570FA554.1090503@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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