From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add libconfig.
Date: Thu, 10 Dec 2015 15:47:10 +0100 [thread overview]
Message-ID: <idjlh928ioh.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <878u52be92.fsf@gnu.org>
Hi Roel,
> This is a patch to add libconfig. It's a simple library without any
> special dependencies. The reason to add this, is because I'm packaging
> other software that depends on libconfig.
>
> I ran guix lint on it, but I still have a problem with TLS, so I'm not
> 100% confident running guix lint is clean. Please let me know if
> something is wrong with the patch.
this looks really good. Thank you.
> From a21ebd71a39bf5000e5809514f0e00185311795d Mon Sep 17 00:00:00 2001
> From: Roel Janssen <roel@gnu.org>
> Date: Thu, 10 Dec 2015 14:45:47 +0100
> Subject: [PATCH] gnu: Add libconfig.
> * gnu/packages/libconfig.scm: New file.
> * gnu-system.am (GNU_SYSTEM_MODULES): Add it.
I have an irrational desire to group similar package expressions in
modules rather than to add new modules. In this case we have
“textutils.scm” and “xml.scm” that seem related.
Someone else should say whether a new module for this is better than
grouping it with one of the above modules. If a new module is indeed
warranted the commit message is perfect.
> +(define-public libconfig
> + (package
> + (name "libconfig")
> + (version "1.5")
> + (source (origin
> + (method url-fetch)
> + (uri (string-append
> + "http://www.hyperrealm.com/libconfig/libconfig-"
> + version ".tar.gz"))
> + (sha256
> + (base32
> + "1xh3hzk63v4y8815lc5209m3s6ms2cpgw4h5hg462i4f1lwsl7g3"))))
> + (build-system gnu-build-system)
> + (home-page "http://www.hyperrealm.com/libconfig/")
> + (synopsis "C/C++ configuration file library")
> + (description
> + "Libconfig is a simple library for manipulating structured configuration
> +files. This file format is more compact and more readable than XML. And
> +unlike XML, it is type-aware, so it is not necessary to do string parsing in
> +application code.")
> + (license license:lgpl2.1)))
The license is actually “lgpl2.1+” because the file headers say this:
“either version 2.1 of the License, or (at your option) any later
version.”
Other than that it looks perfect to me. Thanks again!
~~ Ricardo
next prev parent reply other threads:[~2015-12-10 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 13:54 [PATCH] Add libconfig Roel Janssen
2015-12-10 14:47 ` Ricardo Wurmus [this message]
2015-12-10 15:20 ` Roel Janssen
2015-12-10 15:31 ` Ricardo Wurmus
2015-12-10 15:49 ` Roel Janssen
2015-12-11 20:22 ` Ludovic Courtès
2015-12-11 22:19 ` Roel Janssen
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=idjlh928ioh.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=roel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).