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 11:41:53 +0100 [thread overview]
Message-ID: <20201030114153.4e47cdf8@windsurf.home> (raw)
In-Reply-To: <CAMRc=Mfmk7Bb+eEJ8ikeBfMRir0eBAj7z53eqDK=f-XJqEN5Cg@mail.gmail.com>
On Fri, 30 Oct 2020 11:16:04 +0100
Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> > Well, that is an issue. An application that builds with 1.6 may not
> > build with 1.4, so they are not compatible API-wise, and therefore
> > having libgpiod.mk fall back to 1.4 automatically when the kernel
> > headers are too old is going to potentially break applications that use
> > 1.6-specific APIs.
>
> Versioning of libgpiod just follows the regular MAJOR.MINOR.BUGFIX
> scheme. Major releases break API. Minor releases don't break API but
> (may) introduce new features. Bugfix releases don't change API. I
> think this is the standard for most libraries. So far no buildroot
> package even depends on libgpiod so this could only affect out-of-tree
> users. I'm not sure what the policy here is @buildroot though.
This is perfectly OK. Where it clashes is when a new MAJOR.MINOR
release drops support for kernels older than 5.5, which is a
super-recent kernel version. This prevents from simply updating to the
latest 1.6 release in all situations, causing a compatibility problem
that is quite annoying to handle.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-10-30 10:41 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
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 [this message]
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=20201030114153.4e47cdf8@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