unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: zimoun <zimon.toutoune@gmail.com>, jgart <jgart@dismail.de>,
	help-guix@gnu.org
Subject: Re: build all dependents?
Date: Tue, 22 Nov 2022 20:55:52 +0100	[thread overview]
Message-ID: <87o7syd9uq.fsf@nckx> (raw)
In-Reply-To: <87ilj69380.fsf@contorta>

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

> 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.

How is this not a bug?

A package manager CLI that so routinely lists bogus ‘packages’ 
that break the very same CLI is silly.

We're so used to it happening in Guix that we don't notice, or 
tolerate it when we do, or pile on ad hoc work-arounds because we 
broke the obvious sed to begin with.

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’.

There are probably more.

Kind regards,

T G-R

[0]: Of course these numbers aren't accurate anyway, because 
inheritance.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2022-11-22 20:14 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 [this message]
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=87o7syd9uq.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=jgart@dismail.de \
    --cc=vagrant@debian.org \
    --cc=zimon.toutoune@gmail.com \
    /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).