Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Luca Weiss <luca@lucaweiss.eu>
To: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [ANNOUNCE] libgpiod v2.2
Date: Wed, 23 Oct 2024 18:25:52 +0200	[thread overview]
Message-ID: <12535751.O9o76ZdvQC@g550jk> (raw)
In-Reply-To: <CAMRc=McbWNANVLGSFe6aXjcjMoekUwjov8vM1dSMy03Vp4nXzg@mail.gmail.com>

On Dienstag, 22. Oktober 2024 13:16:17 Mitteleuropäische Sommerzeit Bartosz 
Golaszewski wrote:
> I'm announcing the release of libgpiod v2.2.
> 
> This is a big update for libgpiod bringing in the D-Bus daemon and its
> command-line client, GLib bindings with GObject-introspection and a
> slew of other updates and improvements. The detailed changelog can be
> found in the NEWS file.
> 
> The goal of the D-Bus API is to address the concerns about the lack of
> persistence of GPIO state when the process that requested it exits.
> Now the state can be stored inside the GPIO manager with which clients
> can interact using a well known protocol.
> 
> The release tarball and the git tree can be found over at kernel.org[1][2].
> 
> Bartosz
> 
> [1] https://mirrors.edge.kernel.org/pub/software/libs/libgpiod/
> [2] git://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git
> 
> 

Hi Bartosz!

I'm noticing while packaging for Alpine that the file name of the installed 
lib changed from libgpiod.so.3.1.2 in v2.1.3 to libgpiod.so.3.1.1 in v2.2 - so 
essentially it jumped back.

I'm guessing this is not on purpose and while I don't think it should cause 
issues in the distro, I wanted to make you aware.

Regards
Luca



  reply	other threads:[~2024-10-23 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 11:16 [ANNOUNCE] libgpiod v2.2 Bartosz Golaszewski
2024-10-23 16:25 ` Luca Weiss [this message]
2024-10-23 18:17   ` Bartosz Golaszewski
2024-10-23 23:54     ` Kent Gibson
2024-10-24  8:51       ` Bartosz Golaszewski

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=12535751.O9o76ZdvQC@g550jk \
    --to=luca@lucaweiss.eu \
    --cc=brgl@bgdev.pl \
    --cc=linux-gpio@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox