guix-devel
[Top][All Lists]
Advanced

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

Re: [PATCH] gnu: Add Augeas.


From: Leo Famulari
Subject: Re: [PATCH] gnu: Add Augeas.
Date: Thu, 3 Mar 2016 22:03:27 -0500
User-agent: Mutt/1.5.24 (2015-08-30)

On Thu, Mar 03, 2016 at 05:16:05PM +0100, Ricardo Wurmus wrote:
> 
> Ludovic Courtès <address@hidden> writes:
> 
> > Ricardo Wurmus <address@hidden> skribis:
> >
> >> Leo Famulari <address@hidden> 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



reply via email to

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