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: Thu, 3 Mar 2016 22:03:27 -0500 [thread overview]
Message-ID: <20160304030327.GB30676@jasmine> (raw)
In-Reply-To: <idjh9gny1tm.fsf@bimsb-sys02.mdc-berlin.net>
On Thu, Mar 03, 2016 at 05:16:05PM +0100, Ricardo Wurmus wrote:
>
> Ludovic Courtès <ludo@gnu.org> writes:
>
> > Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
> >
> >> Leo Famulari <leo@famulari.name> writes:
> >>
> >>>> + (build-system gnu-build-system)
> >>>> + ;; Marked as "required" in augeas.pc
> >>>> + (propagated-inputs
> >>>> + `(("libxml2" ,libxml2)))
> >
> > I find it clearer to put the comment right below ‘propagated-inputs’.
> >
> >>> Is there really no way to avoid this?
> >>
> >> I don’t know.
> >
> > The problem is that I don’t think it works to put an absolute file name
> > in the ‘Requires’ field of a ‘.pc’ file, so I don’t think we can avoid
> > it unfortunately.
> >
> > However, since Augeas is a library, the propagated input is acceptable:
> > in practice, people probably won’t have it in their main environment,
> > but rather in a ‘guix environment’ thing, or in a dedicated development
> > profile.
>
> Augeas is both a library and a command line tool. For a command line
> tool propagation is ugly and I’d like to avoid it.
>
> What should I best do in this case?
What is the effect of a wrapper compared to propagation? My
understanding is that the wrapped environment is only visible to the
wrapped binary. Is that correct? If so, it seems less intrusive to the
user's profile.
>
> ~~ Ricardo
next prev parent reply other threads:[~2016-03-04 3:03 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
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 [this message]
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=20160304030327.GB30676@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).