From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 3/8] package/swig: bump version to 3.0.7
Date: Sun, 22 Nov 2015 22:53:12 +0100 [thread overview]
Message-ID: <8737vx66rb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1448134835-27519-3-git-send-email-bernd.kuhls@t-online.de> (Bernd Kuhls's message of "Sat, 21 Nov 2015 20:40:30 +0100")
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/swig/swig.hash | 2 +-
> package/swig/swig.mk | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
> diff --git a/package/swig/swig.hash b/package/swig/swig.hash
> index 98baaa2..62e3d20 100644
> --- a/package/swig/swig.hash
> +++ b/package/swig/swig.hash
> @@ -1,2 +1,2 @@
> # Locally computed:
> -sha256 65e13f22a60cecd7279c59882ff8ebe1ffe34078e85c602821a541817a4317f7 swig-2.0.12.tar.gz
> +sha256 06dc8816a225667ce1eee545af3caf87e1bbaa379c32838d4cea53152514348d swig-3.0.7.tar.gz
> diff --git a/package/swig/swig.mk b/package/swig/swig.mk
> index 6b9b8ae..a2125aa 100644
> --- a/package/swig/swig.mk
> +++ b/package/swig/swig.mk
> @@ -4,8 +4,8 @@
> #
> ################################################################################
> -SWIG_VERSION_MAJOR = 2.0
> -SWIG_VERSION = $(SWIG_VERSION_MAJOR).12
> +SWIG_VERSION_MAJOR = 3.0
> +SWIG_VERSION = $(SWIG_VERSION_MAJOR).7
This is a new major version, does nothing need to change?
It looks like the swig2.0 symlink handling should atleast change as we
now make it swig3.0?
A more detailed commit message on this kind of stuff would be handy.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-11-22 21:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 19:40 [Buildroot] [PATCH/next 1/8] package/boost: bump version to 1.59.0 Bernd Kuhls
2015-11-21 19:40 ` [Buildroot] [PATCH/next 2/8] package/yasm: bump version to 1.3.0 Bernd Kuhls
2015-11-22 21:48 ` Peter Korsgaard
2015-11-21 19:40 ` [Buildroot] [PATCH/next 3/8] package/swig: bump version to 3.0.7 Bernd Kuhls
2015-11-22 21:53 ` Peter Korsgaard [this message]
2015-11-21 19:40 ` [Buildroot] [PATCH/next 4/8] package/libass: bump version to 0.13.0 Bernd Kuhls
2015-11-22 21:56 ` Peter Korsgaard
2015-11-21 19:40 ` [Buildroot] [PATCH/next 5/8] package/libfribidi: bump version to 0.19.7 Bernd Kuhls
2015-11-22 21:56 ` Peter Korsgaard
2015-11-21 19:40 ` [Buildroot] [PATCH/next 6/8] package/libglew: bump version to 1.13.0 Bernd Kuhls
2015-11-22 21:59 ` Peter Korsgaard
2015-11-21 19:40 ` [Buildroot] [PATCH/next 7/8] package/tvheadend: bump version Bernd Kuhls
2015-11-22 22:00 ` Peter Korsgaard
2015-11-21 19:40 ` [Buildroot] [PATCH/next 8/8] package/{mesa3d, mesa3d-headers}: bump version to 11.0.6 Bernd Kuhls
2015-11-22 22:01 ` Peter Korsgaard
2015-11-22 21:47 ` [Buildroot] [PATCH/next 1/8] package/boost: bump version to 1.59.0 Peter Korsgaard
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=8737vx66rb.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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