Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libgpiod: bump  version to 1.6
Date: Fri, 30 Oct 2020 09:19:29 +0100	[thread overview]
Message-ID: <20201030091929.18f77130@windsurf.home> (raw)
In-Reply-To: <57-5f9bc680-3-4a87f08@125885651>

Hello,

On Fri, 30 Oct 2020 08:53:18 +0100
"Michael Nosthoff" <buildroot@heine.tech> wrote:

> Will 1.4.x still work with 5.10 kernels? I guess the old API will
> just be deprecated for a while?
> 
> So I guess we have two possibilities going forward: 
> 
> - Use the version switch I proposed and even extend it when 2.0 and
> headers 5.10 are released or
> - Stay on the 1.4.x branch until linux 5.5 is the oldest supported
> version (if this is possible).

What worries a bit with supporting both 1.4 and 1.6, and in the future
say 1.4, 1.6 and 2.0 is that newer versions are likely to introduce new
APIs. Applications may rely on such new APIs. When the kernel headers
are recent enough, a recent version of libgpiod will be used, and such
applications will build properly. But as soon as soon builds a system
with older kernel headers, libgpiod will downgrade to an older version,
providing potentially less APIs, and therefore breaking any application
using them.

This strategy of not supporting older kernels in newer versions of
libgpiod also means that libgpiod should not introduce any new public
API... Otherwise the maintenance burden that libgpiod avoids by not
supporting older kernels is a maintenance burden that will fall on the
shoulders of users of libgpiod, who will have to make conditional
switches depending on whether libgpiod 1.4, 1.6 or 2.0 is used.

I am still highly doubtful of the strategy chosen by upstream libgpiod
here.

Best regards,

Thomas Petazzoni
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-10-30  8:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 11:06 [Buildroot] [PATCH] package/libgpiod: bump version to 1.6 buildroot at heine.tech
2020-10-29 12:50 ` Thomas Petazzoni
2020-10-29 13:06   ` Michael Nosthoff
2020-10-29 13:12     ` Bartosz Golaszewski
2020-10-29 13:13     ` Thomas Petazzoni
2020-10-29 13:41       ` Bartosz Golaszewski
2020-10-30  7:53         ` Michael Nosthoff
2020-10-30  8:19           ` Thomas Petazzoni [this message]
2020-10-30  8:42             ` Bartosz Golaszewski
2020-10-30  9:15               ` Thomas Petazzoni
2020-10-30  9:25                 ` Bartosz Golaszewski
2020-10-30  9:34                   ` Thomas Petazzoni
2020-10-30 10:16                     ` Bartosz Golaszewski
2020-10-30 10:41                       ` Thomas Petazzoni
2020-10-30 10:53                         ` Bartosz Golaszewski
2020-11-03 20:25                           ` Arnout Vandecappelle
2020-11-03 20:56                             ` Bartosz Golaszewski
2020-11-30 20:31                               ` Bartosz Golaszewski
2020-12-02 16:57                                 ` Nicolas Cavallari
2020-10-30  8:25           ` Bartosz Golaszewski
2020-11-02 10:21 ` [Buildroot] [PATCH v2] package/libgpiod: bump version to 1.4.5 Michael Nosthoff
2020-11-02 10:27   ` [Buildroot] [PATCH v3] " Michael Nosthoff

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=20201030091929.18f77130@windsurf.home \
    --to=thomas.petazzoni@bootlin.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