unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: bjoern.hoefling@bjoernhoefling.de
Cc: Guix-devel <guix-devel@gnu.org>, ng0 <ng0@n0.is>
Subject: Re: Extracting a reachability path out of a (package) DAG
Date: Tue, 17 Jul 2018 17:09:47 +0200	[thread overview]
Message-ID: <CAE4v=pj+M5Lf-K-ydXfMKaELqYYWRKBgKTuCbDFRYxnKE=s2og@mail.gmail.com> (raw)
In-Reply-To: <20180717123211.175f52ac@alma-ubu>

[-- Attachment #1: Type: text/plain, Size: 814 bytes --]

Björn Höfling <bjoern.hoefling@bjoernhoefling.de> ezt írta (időpont: 2018.
júl. 17., K, 12:32):

> On Tue, 17 Jul 2018 08:24:24 +0000
> Nils Gillmann <ng0@n0.is> wrote:
>
>
> > To add to this idea:
> > abyayala$ nix why-depends --help
> > Usage: nix why-depends <FLAGS>... <PACKAGE> <DEPENDENCY>
> >
> > Summary: show why a package has another package in its closure.
>
> [..]
>
> > Would it be useful to have a guix package subcommand which replicates
> > this?
>
>
> Yeah, would be nice. Because that was missing, I created that script
> for me.
>
> Björn
>

Thanks, Björn. I've recently had the same problem, and I was about to write
this script once we moved to jdk8. Now I don't have to do it any more :)
This is very useful, it helps so much in bootstrapping related work.

[-- Attachment #2: Type: text/html, Size: 1227 bytes --]

  reply	other threads:[~2018-07-17 15:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17  8:10 Extracting a reachability path out of a (package) DAG Björn Höfling
2018-07-17  8:22 ` Pierre Neidhardt
2018-07-17 10:29   ` Björn Höfling
2018-07-17  8:24 ` Nils Gillmann
2018-07-17 10:32   ` Björn Höfling
2018-07-17 15:09     ` Gábor Boskovits [this message]
2018-07-21 21:55       ` Pierre Neidhardt
2018-07-22 18:53         ` Alex Kost
2018-07-22 18:59           ` Pierre Neidhardt
2018-07-22 19:18             ` Björn Höfling
2018-07-23 13:09 ` Ludovic Courtès
2018-08-04  3:54 ` Chris Marusich

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='CAE4v=pj+M5Lf-K-ydXfMKaELqYYWRKBgKTuCbDFRYxnKE=s2og@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    --cc=guix-devel@gnu.org \
    --cc=ng0@n0.is \
    /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).