From: Michael Nosthoff <buildroot@heine.tech>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libgpiod: bump to version 1.6.2
Date: Mon, 01 Feb 2021 11:29:09 +0100 [thread overview]
Message-ID: <6b1-6017d800-5-32d73800@194734800> (raw)
In-Reply-To: <CAMRc=MfcP2OHngNzwM+L3YbmhhcvSGcmuGdau2dH_wG5pgQZqQ@mail.gmail.com>
Hi Bartosz,
On Monday, February 01, 2021 10:55 CET, Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> On Mon, Feb 1, 2021 at 10:13 AM Michael Nosthoff <buildroot@heine.tech> wrote:
> >
> > -LIBGPIOD_VERSION = 1.4.5
> > +# Be careful when bumping versions.
> > +# Dependency on kernel header versions may change.
>
> You can remove this comment - for v1.6.x I won't change the headers
> version requirement anymore and vor v2.x we'll start bundling the
> kernel header with the library. I also don't plan on making any new
> feature releases for the v1.x series.
>
perfect, then I'll drop that.
> > +LIBGPIOD_VERSION = 1.6.2
> > LIBGPIOD_SOURCE = libgpiod-$(LIBGPIOD_VERSION).tar.xz
> > LIBGPIOD_SITE = https://www.kernel.org/pub/software/libs/libgpiod
> > LIBGPIOD_LICENSE = LGPL-2.1+
> > LIBGPIOD_LICENSE_FILES = COPYING
> > LIBGPIOD_INSTALL_STAGING = YES
> > LIBGPIOD_DEPENDENCIES = host-pkgconf
> > +LIBGPIOD_CONF_OPTS = --disable-tests
> >
>
> Maybe add an option to build them conditionally? Like yocto's ptest
> distro feature?
>
I'm not sure if this fits into buildroot's scope. What would be the benefit for the user? Maybe Thomas has an opinion on that?
From the dependencies I see we currently don't have catch2 in BR. So this might be the showstopper atm.
Regards,
Michael
next prev parent reply other threads:[~2021-02-01 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 9:12 [Buildroot] [PATCH] package/libgpiod: bump to version 1.6.2 Michael Nosthoff
2021-02-01 9:55 ` Bartosz Golaszewski
2021-02-01 10:29 ` Michael Nosthoff [this message]
2021-02-01 13:39 ` Michael Nosthoff
2021-02-02 15:41 ` 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=6b1-6017d800-5-32d73800@194734800 \
--to=buildroot@heine.tech \
--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