unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: jgart <jgart@dismail.de>, Guix Help <help-guix@gnu.org>
Subject: Re: build all dependents?
Date: Tue, 22 Nov 2022 16:20:14 +0100	[thread overview]
Message-ID: <86v8n7c8y9.fsf@gmail.com> (raw)
In-Reply-To: <20221121190635.GB23435@dismail.de>

Hi,

On Mon, 21 Nov 2022 at 19:06, jgart <jgart@dismail.de> wrote:

> is there a command to build all dependents of a package?

[...]

> $ guix refresh python-identify -l
> Building the following 14 packages would ensure 28 dependent packages
> are rebuilt: python-multivelo@0.1.2 repo2docker@2021.08.0
> python-matplotlib-documentation@3.5.2
> python-numpy-documentation@1.21.6 jami-docs@0.0.0-0.b00574b mdpo@0.3.6
> python-flask-combo-jsonapi@1.1.0 onionshare@2.5 python-jupytext@1.14.1
> python-minikanren@1.0.1 python-miio@0.5.11 python-interrogate@1.5.0
> pre-commit@2.20.0 babi@1.5.3 

   $ guix build $(guix refresh python-identify -l | cut -f2 -d':')


> I'd also like to filter out packages from guixrus. babi@1.5.3 is in guixrus.

From the command-line, it can be tedious to filter.  I would go with a
manifest.  Although, I am always confused by unexported bindings.  This,

    (define list-dependents (@@ (guix scripts refresh) list-dependents))

returns,

--8<---------------cut here---------------start------------->8---
/tmp/manifest.scm:6:3: error: list-dependents: unbound variable
hint: Did you forget a `use-modules' form?
--8<---------------cut here---------------end--------------->8---

but that’s the way I would do: list dependent packages, then apply some
filter based on module name (location).

Cheers,
simon



  reply	other threads:[~2022-11-22 15:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22  1:06 build all dependents? jgart
2022-11-22 15:20 ` zimoun [this message]
2022-11-22 19:52   ` Vagrant Cascadian
2022-11-22 19:55     ` Tobias Geerinckx-Rice
2022-11-23  9:47       ` zimoun
2022-11-22 20:06 ` Felix Lechner via
2022-11-22 20:29   ` jgart
2022-11-22 20:31     ` jgart

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=86v8n7c8y9.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=jgart@dismail.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.
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).