From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: yegorslists--- via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v2] package/lpac: new package
Date: Sat, 17 May 2025 17:03:13 +0200 [thread overview]
Message-ID: <20250517170313.74860009@windsurf> (raw)
In-Reply-To: <20250430055956.288191-1-yegorslists@googlemail.com>
Hello Yegor,
On Wed, 30 Apr 2025 07:59:56 +0200
yegorslists--- via buildroot <buildroot@buildroot.org> wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Thanks for your patch, which I have applied, with one small change (see
below).
But out of curiosity, could you explain what LPAC is useful for? I
tried to read a bit on the topic, but it's quite confusing. In what
situation is LPAC needed, on embedded Linux devices?
> +LPAC_VERSION = 2.2.1
> +LPAC_SITE = $(call github,estkme-group,lpac,v$(LPAC_VERSION))
> +LPAC_LICENSE = LGPL-2.0+ (library), AGPL-3.0 (programs), MIT (cjson)
The library license is LGPL-2.1+, so I fixed that up.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-05-17 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 5:59 [Buildroot] [PATCH v2] package/lpac: new package yegorslists--- via buildroot
2025-05-17 15:03 ` Thomas Petazzoni via buildroot [this message]
2025-05-17 21:00 ` Yegor Yefremov
2025-05-18 7:06 ` Thomas Petazzoni via buildroot
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=20250517170313.74860009@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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