packages->manifest can lose the desired package output

I've been fighting my manifest to try to get "git" and "git:send-email"

both included, while using package transformations. For the sake of

brevity, here's a stripped down version of my manifest:

(packages->manifest

(map specification->package+output

'("git" "git:send-email")))

Here's what I learned from some experimentation:

(cmd)scheme@(guile-user)> (specification->package+output "git:send-email")

$14 = #<package git@2.32.0 gnu/packages/version-control.scm:176 7f730e918320>

$15 = "send-email"

(ins)scheme@(guile-user)> (list (specification->package+output "git:send-email"))

$16 = (#<package git@2.32.0 gnu/packages/version-control.scm:176 7f730e918320>)

(ins)scheme@(guile-user)> (list (specification->package+output "git"))

$17 = (#<package git@2.32.0 gnu/packages/version-control.scm:176 7f730e918320>)

Meanwhile, (specifications->manifest '("git" "git:send-email")) does

actually return a manifest with both the "out" and the "send-email"

outputs of git.

(package->manifest-entry (specification->package+output "git:send-email"))

returns a manifest entry for "git:out" and

(package->manifest-entry git "send-email") returns a manifest entry for

"git:send-email".

--

Efraim Flashner <efraim@flashner.co.il> ????? ?????

GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351

Confidentiality cannot be guaranteed on emails sent or received unencrypted

Hi Efraim,

Am Freitag, den 10.09.2021, 12:34 +0300 schrieb Efraim Flashner:

I think for this use of specification->package+output you need to

compose it with list like (compose list specification->package+output).

The reason you observe this behaviours is that specification-

entry expects a single value which is either a package or a list of the

form (package "output").

Regards

Hi,

Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:

Yes, and Guile truncates multiple-value returns by default:

Ludo’.

tags 50501 notabug

close 50501

quit