From: cp0613@linux.alibaba.com
To: ju.o@free.fr
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/iniparser: new package
Date: Wed, 4 Mar 2026 15:05:16 +0800 [thread overview]
Message-ID: <20260304070516.1677-1-cp0613@linux.alibaba.com> (raw)
In-Reply-To: <b02a221e1a4914633565797b5f211029@free.fr>
On Tue, 03 Mar 2026 19:08:41 +0100, ju.o@free.fr wrote:
> > From: Chen Pei <cp0613@linux.alibaba.com>
> >
> > The iniparser is a simple C library offering ini file parsing services.
> >
> > ndctl[1] requires it.
> >
> > [1] https://github.com/pmem/ndctl
> >
> > Signed-off-by: Chen Pei <cp0613@linux.alibaba.com>
> > ---
> [...]
> > diff --git a/package/iniparser/iniparser.mk
> > b/package/iniparser/iniparser.mk
> > new file mode 100644
> > index 0000000000..9034a1cb78
> > --- /dev/null
> > +++ b/package/iniparser/iniparser.mk
> > @@ -0,0 +1,14 @@
> > +################################################################################
> > +#
> > +# iniparser
> > +#
> > +################################################################################
> > +
> > +INIPARSER_VERSION = v4.2.6
> > +INIPARSER_SITE =
> > https://gitlab.com/iniparser/iniparser/-/archive/$(INIPARSER_VERSION)
> > +INIPARSER_SOURCE = iniparser-$(INIPARSER_VERSION).tar.gz
>
> Could you move the "v" from the _VERSION to _SITE and update _SOURCE,
> please? This will allow our version monitoring scripts to work better.
> We should preferably have:
>
> INIPARSER_VERSION = 4.2.6
> INIPARSER_SITE =
> https://gitlab.com/iniparser/iniparser/-/archive/v$(INIPARSER_VERSION)
> INIPARSER_SOURCE = iniparser-v$(INIPARSER_VERSION).tar.gz
>
> Note: your initial submission was also reporting an error, which
> should be fixed indirectly with the change I propose. Please make
> sure to run the command "utils/docker-run make check-package" before
> sending patches. See:
> https://nightly.buildroot.org/manual.html#_preparing_a_patch_series
>
> > +INIPARSER_INSTALL_STAGING = YES
> > +INIPARSER_LICENSE = MIT
> > +INIPARSER_LICENSE_FILES = LICENSE
> > +
> > +$(eval $(cmake-package))
> > --
> > 2.50.1
>
> Also, quoting the Buildroot documentation at:
> https://nightly.buildroot.org/manual.html#DEVELOPERS
> """
> We ask developers adding new packages, new boards, or generally new
> functionality in Buildroot, to register themselves in the DEVELOPERS
> file. As an example, we expect a developer contributing a new package to
> include in his patch the appropriate modification to the DEVELOPERS
> file.
> """
>
> Note that will received emails from the autobuilders in
> case of build failures, and from other developers using
> the get-developers script.
>
> Could you add a new entry in the DEVELOPERS file registering
> yourself to this new package?
>
> Could you send an updated v2 patch with those changes, please?
>
Hi, Julien,
Thank you for your review and reminder. I will send an v2 patch,
update iniparser.mk, and add a new entry in the DEVELOPERS.
Thanks,
Pei
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-03-04 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 9:50 [Buildroot] [PATCH] package/iniparser: new package cp0613
2026-03-03 18:08 ` Julien Olivain via buildroot
2026-03-04 7:05 ` cp0613 [this message]
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=20260304070516.1677-1-cp0613@linux.alibaba.com \
--to=cp0613@linux.alibaba.com \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.