emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#45398: closed ([PATCH 0/2] xfsprogs 5.10.0 & libinih)


From: GNU bug Tracking System
Subject: bug#45398: closed ([PATCH 0/2] xfsprogs 5.10.0 & libinih)
Date: Thu, 24 Dec 2020 20:21:01 +0000

Your message dated Thu, 24 Dec 2020 15:20:24 -0500
with message-id <X+T4CDnlouoVZNUk@jasmine.lan>
and subject line Re: [bug#45398] [PATCH 1/2] gnu: Add libinih.
has caused the debbugs.gnu.org bug report #45398,
regarding [PATCH 0/2] xfsprogs 5.10.0 & libinih
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
45398: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=45398
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH 0/2] xfsprogs 5.10.0 & libinih Date: Wed, 23 Dec 2020 18:12:04 +0100
Hello,

the new xfsprogs version now requires the
inih parser library.

The first patch add that new package and
the second one updates xfsprogs with it.

Please review, as this is my first contact
with the meson build system.

Also the license file contains "new BSD", so
I chose "bsd-4"...

Tchuss

-- 
Vincent Legoll



--- End Message ---
--- Begin Message --- Subject: Re: [bug#45398] [PATCH 1/2] gnu: Add libinih. Date: Thu, 24 Dec 2020 15:20:24 -0500
On Wed, Dec 23, 2020 at 06:14:25PM +0100, Vincent Legoll wrote:
> * gnu/packages/linux.scm (libinih): New variable.

Thanks!

> +    (description "The inih (INI Not Invented Here) library is a simple .INI 
> file
> +parser written in C. It's only a couple of pages of code, and it was 
> designed to
> +be small and simple, so it's good for embedded systems. It's also more or 
> less
> +compatible with Python's ConfigParser style of .INI files, including RFC
> +822-style multi-line syntax and name: value entries.")
> +    (license license:bsd-4)))

I fixed the issues reported by `guix lint`, corrected the license to
bsd-3, and pushed both patches 9325171df468f6a84ac7cdab01f0c6461ff1c7bc


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]