From: zimoun <zimon.toutoune@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>,
Vagrant Cascadian <vagrant@debian.org>
Cc: jgart <jgart@dismail.de>, help-guix@gnu.org
Subject: Re: build all dependents?
Date: Wed, 23 Nov 2022 10:47:27 +0100 [thread overview]
Message-ID: <86zgciatow.fsf@gmail.com> (raw)
In-Reply-To: <87o7syd9uq.fsf@nckx>
Hi,
On Tue, 22 Nov 2022 at 20:55, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>> This sometimes requires some manual fiddling
>
> Thanks for highlighting that. I've never encountered it.
>
> This is similar to another recent bug report, where ‘guix show’
> listed something as depending on a hidden package. Or something
> like that.
If you are referring to bug#59278, the bug is on the package definition
side. As explained here [1], the ’hidden’ properties is dropped out at
one ’inherit’.
1: http://issues.guix.gnu.org/msgid/87h6yz46wp.fsf@gmail.com
> Two possible solutions:
>
> - Hide hidden packages. This makes the most sense to me. You'd
> still report accurate[0] numbers for ‘guix refresh -l’.
>
> - Allow referring to hidden packages in some contexts, or maybe
> all contexts, and keep listing them in ‘advanced’ tools like
> ‘guix refresh -l’.
I agree that what is hidden is not clear. Maybe a marker could be added
when displaying the hidden packages in “guix refresh -l”. It would
allow to filter them out.
Or we could separate the regular packages to the hidden one,
--8<---------------cut here---------------start------------->8---
$ guix refresh -l guile-ssh
Building the following 19 packages would ensure 26 dependent packages are rebuilt: emacs-guix@0.5.2-6.cf5b7a4 guile-imanifest@0.0.0-0.ccd5a21 cl-ospm@0.0.1 gwl@0.5.0 guix-jupyter@0.2.2 guix-build-coordinator@0-65.26fe4a7 guix-build-coordinator-agent-only@0-65.26fe4a7 gwl-next@0.5.0-1.706a089 nar-herder@0-9.5acfcc0 guix-modules@0.1.0 hpcguix-web@0.2.0 guix-data-service@0.0.1-33.ee73d2c numix-gtk-theme@2.6.7 arc-theme@20220405 gnome-shell-extension-gsconnect@50 gnome-terminal@3.44.1 gnome@42.4 cuirass@1.1.0-11.9f08035 '(@@ (gnu packages package-management) guix-daemon)'
--8<---------------cut here---------------end--------------->8---
Well, maybe a rework of the submission #58824 [1].
1: <http://issues.guix.gnu.org/msgid/20221027212706.21680-1-paren@disroot.org>
Cheers,
simon
next prev parent reply other threads:[~2022-11-23 10:27 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
2022-11-22 19:52 ` Vagrant Cascadian
2022-11-22 19:55 ` Tobias Geerinckx-Rice
2022-11-23 9:47 ` zimoun [this message]
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=86zgciatow.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
--cc=me@tobias.gr \
--cc=vagrant@debian.org \
/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).