All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Sergey Bobrenok <bobrofon@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/sdbus-cpp: bump to version 1.1.0
Date: Sat, 22 Jan 2022 21:03:41 +0100	[thread overview]
Message-ID: <20220122200341.GG3621364@scaer> (raw)
In-Reply-To: <20220122124111.103131-1-bobrofon@gmail.com>

Sergey, All,

On 2022-01-22 15:41 +0300, Sergey Bobrenok spake thusly:
> Signed-off-by: Sergey Bobrenok <bobrofon@gmail.com>
> ---
>  package/sdbus-cpp/sdbus-cpp.hash | 3 ++-
>  package/sdbus-cpp/sdbus-cpp.mk   | 6 +++---
>  2 files changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/package/sdbus-cpp/sdbus-cpp.hash b/package/sdbus-cpp/sdbus-cpp.hash
> index 8b87653dfd..3a0e863a86 100644
> --- a/package/sdbus-cpp/sdbus-cpp.hash
> +++ b/package/sdbus-cpp/sdbus-cpp.hash
> @@ -1,3 +1,4 @@
>  # Locally computed:
> -sha256  0fd575ae0f463773dd9141242d1133731e2b780fd6526650ce992ba711d88628  v0.8.3.tar.gz
> +sha256  35e939fdd9c796522702c9c8762dd59b5c47f3440c01ba9feb9921c042780b55  v1.1.0.tar.gz
>  sha256  20c17d8b8c48a600800dfd14f95d5cb9ff47066a9641ddeab48dc54aec96e331  COPYING
> +sha256  be43debbf06a38325616054a39e44ed5afde4ed21b99de197488a4a306d47e39  COPYING-LGPL-Exception
> diff --git a/package/sdbus-cpp/sdbus-cpp.mk b/package/sdbus-cpp/sdbus-cpp.mk
> index 24904ee26f..e0fbc5c856 100644
> --- a/package/sdbus-cpp/sdbus-cpp.mk
> +++ b/package/sdbus-cpp/sdbus-cpp.mk
> @@ -4,12 +4,12 @@
>  #
>  ################################################################################
>  
> -SDBUS_CPP_VERSION = 0.8.3
> +SDBUS_CPP_VERSION = 1.1.0
>  SDBUS_CPP_SOURCE = v$(SDBUS_CPP_VERSION).tar.gz
>  SDBUS_CPP_SITE = $(call github,Kistler-Group,sdbus-cpp,v$(SDBUS_CPP_VERSION))
>  SDBUS_CPP_INSTALL_STAGING = YES
>  SDBUS_CPP_DEPENDENCIES = host-pkgconf systemd
> -SDBUS_CPP_LICENSE = LGPL-2.1+
> -SDBUS_CPP_LICENSE_FILES = COPYING
> +SDBUS_CPP_LICENSE = LGPL-2.1+ with exception (headers)
> +SDBUS_CPP_LICENSE_FILES = COPYING COPYING-LGPL-Exception

Thanks for noticing the update in the licensing terms. :-)

Applied to master, thanks.

Regards,
Yann E. MORIN.

>  $(eval $(cmake-package))
> -- 
> 2.31.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-01-22 20:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22 12:41 [Buildroot] [PATCH 1/1] package/sdbus-cpp: bump to version 1.1.0 Sergey Bobrenok
2022-01-22 20:03 ` Yann E. MORIN [this message]

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=20220122200341.GG3621364@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=bobrofon@gmail.com \
    --cc=buildroot@buildroot.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.