From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add Augeas.
Date: Fri, 22 Jan 2016 15:29:34 -0500 [thread overview]
Message-ID: <20160122202934.GB27435@jasmine> (raw)
In-Reply-To: <idjoacf9dmg.fsf@bimsb-sys02.mdc-berlin.net>
On Thu, Jan 21, 2016 at 04:05:43PM +0100, Ricardo Wurmus wrote:
> From 546a8651db1c420fee841a2da6474593e4c9aa93 Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
> Date: Thu, 21 Jan 2016 16:03:26 +0100
> Subject: [PATCH] gnu: Add Augeas.
>
> * gnu/packages/augeas.scm: New file.
> * gnu-system.am (GNU_SYSTEM_MODULES): Add it.
[...]
> +(define-public augeas
[...]
> + (build-system gnu-build-system)
> + ;; Marked as "required" in augeas.pc
> + (propagated-inputs
> + `(("libxml2" ,libxml2)))
Is there really no way to avoid this?
> + (inputs
> + `(("readline" ,readline)))
> + (native-inputs
> + `(("pkg-config" ,pkg-config)))
> + (home-page "http://augeas.net/")
> + (synopsis "Edit configuration files programmatically")
> + (description
> + "Augeas is a library and command line tool for programmatically editing
> +configuration files in a controlled manner. Augeas exposes a tree of all
> +configuration settings and a simple local API for manipulating the tree.
> +Augeas then modifies underlying configuration files according to the changes
> +that have been made to the tree; it does as little modeling of configurations
> +as possible, and focuses exclusivley on transforming the tree-oriented syntax
> +of its public API to the myriad syntaxes of individual configuration files.")
> + (license license:lgpl2.1+)))
> --
> 2.1.0
>
>
next prev parent reply other threads:[~2016-01-22 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 15:05 [PATCH] gnu: Add Augeas Ricardo Wurmus
2016-01-22 20:29 ` Leo Famulari [this message]
2016-02-02 15:50 ` Ricardo Wurmus
2016-02-02 17:13 ` Tobias Geerinckx-Rice
2016-02-02 19:11 ` Ricardo Wurmus
2016-02-03 9:37 ` Ludovic Courtès
2016-03-03 16:16 ` Ricardo Wurmus
2016-03-04 3:03 ` Leo Famulari
2016-03-04 8:21 ` Ricardo Wurmus
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=20160122202934.GB27435@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).