unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: email@msavoritias.me, 73599@debbugs.gnu.org
Cc: ludo@gnu.org
Subject: bug#73599: packages from store paths don't propagate propagated-inputs
Date: Thu, 03 Oct 2024 09:29:25 +0000	[thread overview]
Message-ID: <84D6620E-38AC-4F18-93F1-0F8AEC7D8D4C@tobias.gr> (raw)
In-Reply-To: <2214f032-e5d5-4592-b05a-c7134cfcba62@msavoritias.me>

Heyo,

On 3 October 2024 07:39:27 UTC, MSavoritias <email@msavoritias.me> wrote:
>Tobias Geerinckx-Rice kirjoitti 2.10.2024 klo 21.22:
>> is, or is expected to be, a supported way to install packages?  Packages have more metadata attached to them than store items.  I don't think that propagation is recorded in the Nix database.  Nor do I think it should be just to support this hack.
>
>It actually is mentioned explicitly in the manual. https://guix.gnu.org/manual/devel/en/html_node/Invoking-guix-package.html

I think I was misunderstood.  That is the part that needs improvement.  It may not 'explicitly' say that propagation will work in both cases, but the flow strongly implies it.

What I'm not aware of is any documentation that 'installing a store item'  is not the same as 'installing a package'.  It's a lossy transformation.

See also:

  $ guix package -I sbcl-typo
  $ guix install sbcl-typo &>/dev/null
  $ guix package -I sbcl-typo
  sbcl-typo       0.0.0-0.0e88349 out     /gnu/store/67nkzm5mw4ma39na24l9rv98gkfh3nbg-sbcl-typo-0.0.0-0.0e88349
  $ guix package -r sbcl-typo -i $(guix build sbcl-typo) &>/dev/null
  $ guix package -I sbcl-typo
  sbcl-typo-0.0.0 0.0e88349       out     /gnu/store/67nkzm5mw4ma39na24l9rv98gkfh3nbg-sbcl-typo-0.0.0-0.0e88349
  $ guix package -r sbcl-typo
  guix package: error: package 'sbcl-typo' not found in profile

Because  <https://gitlab.oit.duke.edu/duke-guix/guix/-/blob/master/guix/scripts/package.scm?ref_type=heads#L619> — I guess Savannah's down again.

Store items just aren't packages.

>Personally i could go either way.

I don't think you can, not *without* extending the database schema or otherwise adding the missing metadata back to the store item though, e.g., a hidden Scheme file, i.e., overkill.  I'd love to be proven wrong.

Otherwise, the documentation-bug way is the only realistic way.



Kind regards,

T G-R

Sent on the go.  Excuse or enjoy my brevity.




  parent reply	other threads:[~2024-10-03  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 14:46 bug#73599: packages from store paths don't propagate propagated-inputs MSavoritias
2024-10-02 18:22 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2024-10-03  7:39   ` MSavoritias
2024-10-03  8:07     ` MSavoritias
2024-10-03  9:29     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2024-10-03  9:34       ` MSavoritias

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=84D6620E-38AC-4F18-93F1-0F8AEC7D8D4C@tobias.gr \
    --to=bug-guix@gnu.org \
    --cc=73599@debbugs.gnu.org \
    --cc=email@msavoritias.me \
    --cc=ludo@gnu.org \
    --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 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).