all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: jgart <jgart@dismail.de>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, help-guix@gnu.org
Subject: Re: language server doesn't let me emote
Date: Sat, 06 Aug 2022 20:02:39 +0200	[thread overview]
Message-ID: <87fsi9xn41.fsf@web.de> (raw)
In-Reply-To: <20220806122425.GB19215@gac>

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


jgart <jgart@dismail.de> writes:

> Should I keep only one because of propagated-inputs but then doesn't
> that break the declarativeness of wanting a particular package without
> worrying about dep bleed?
>
> ¯\_(ツ)_/¯

I also used to run into such problems pretty often.

The only way I found to break such cycles reliably (without in the end
putting tens of packages into "update also" list) is to create a
manifest-file and always install new packages by adding them to the
manifest and then installing the manifest:

    guix package  --fallback -k -m ~/fluss-guix.manifest

To create the manifest, you can nowadays just export it:

    guix package --export-manifest > ~/fluss-guix.manifest

This works, but is hard to tell newcomers, so I’d much prefer having
install show me the list of all other packages that need to be updated
to install the package in question and being asked yes or no to that.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

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

  reply	other threads:[~2022-08-06 18:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 14:02 language server doesn't let me emote jgart
2022-08-06 14:52 ` Tobias Geerinckx-Rice
2022-08-06 16:09   ` jgart
2022-08-06 16:19     ` Tobias Geerinckx-Rice
2022-08-06 16:34       ` Tobias Geerinckx-Rice
2022-08-06 17:24         ` jgart
2022-08-06 18:02           ` Dr. Arne Babenhauserheide [this message]
2022-08-06 17:53 ` Akib Azmain Turja

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fsi9xn41.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=help-guix@gnu.org \
    --cc=jgart@dismail.de \
    --cc=me@tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.