oid pulling in
a big GUI package when I chose a bare-bones system, since I had to
compile it a few times while hydra was recovering. I always have seen
the term "reverse dependencies" used to refer to that concept.
> I'd also like to point out that you can already use 'guix gc
On 2016-08-12 11:24, Chris Marusich wrote:
Eric Bavier writes:
On 2016-08-11 09:43, Vincent Legoll wrote:
Hello,
I'm trying to understand which package(s) depends on some other
package,
kind of the reverse of what guix graph does (I think).
I think that `guix refresh --list-dependent foo`
Eric Bavier writes:
> On 2016-08-11 09:43, Vincent Legoll wrote:
>> Hello,
>>
I'm trying to understand which package(s) depends on some other
package,
kind of the reverse of what guix graph does (I think).
>>>
>>> I think that `guix refresh --list-dependent foo` is what you are
>>>
On Fri, Aug 12, 2016 at 11:55 AM, Thompson, David
wrote:
> I'd also like to point out that you can already use 'guix gc
> --referrers /gnu/store/-foo-1.0' to find out which store items
> depend on the one passed in.
I realize this is redundant with what I wrote above. Hasty writing...
Sorry
On Fri, Aug 12, 2016 at 5:27 AM, Vincent Legoll
wrote:
> Hello,
>
>> I think you mean inkscape is pulled when you build the system. Then you
>> will not find it like this. It is needed to build the fancy grub image,
>> and it is "pulled" by the system building code (specifically by
>> 'svg->png'
Eric Bavier writes:
> On 2016-08-12 11:24, Chris Marusich wrote:
>> Eric Bavier writes:
>>
>>> On 2016-08-11 09:43, Vincent Legoll wrote:
Hello,
>> I'm trying to understand which package(s) depends on some other
>> package,
>> kind of the reverse of what guix graph does (I
Hello,
> I think you mean inkscape is pulled when you build the system. Then you
> will not find it like this. It is needed to build the fancy grub image,
> and it is "pulled" by the system building code (specifically by
> 'svg->png' procedure in (gnu system grub) module). If you want to avoid
Vincent Legoll (2016-08-11 17:43 +0300) wrote:
> Hello,
>
>>> I'm trying to understand which package(s) depends on some other package,
>>> kind of the reverse of what guix graph does (I think).
>>
>> I think that `guix refresh --list-dependent foo` is what you are asking
>> for, or at least it's c
> "VL" == Vincent Legoll writes:
VL> Hello,
>>> I'm trying to understand which package(s) depends on some other package,
>>> kind of the reverse of what guix graph does (I think).
>>
>> I think that `guix refresh --list-dependent foo` is what you are asking
>> for, or at least it's close. W
On 2016-08-11 09:43, Vincent Legoll wrote:
Hello,
I'm trying to understand which package(s) depends on some other
package,
kind of the reverse of what guix graph does (I think).
I think that `guix refresh --list-dependent foo` is what you are
asking
for, or at least it's close. We use it t
Hello,
>> I'm trying to understand which package(s) depends on some other package,
>> kind of the reverse of what guix graph does (I think).
>
> I think that `guix refresh --list-dependent foo` is what you are asking
> for, or at least it's close. We use it to learn what will need to be
> rebuilt
On Sat, Jul 16, 2016 at 11:58:51AM +0200, Vincent Legoll wrote:
> Hello,
>
> I'm trying to understand which package(s) depends on some other package,
> kind of the reverse of what guix graph does (I think).
I think that `guix refresh --list-dependent foo` is what you are asking
for, or at least i
Hello,
I'm trying to understand which package(s) depends on some other package,
kind of the reverse of what guix graph does (I think).
--
Vincent Legoll
13 matches
Mail list logo
