Re: GWL 0.5 fails with plain packages

[Liliana Marie Prikler]

Am Freitag, dem 29.07.2022 um 11:40 -0400 schrieb Olivier Dion:
> Please try the following patch:
> --8<---------------cut here---------------start------------->8---
> diff --git a/gwl/processes.scm b/gwl/processes.scm
> index 2452d1f..4207f51 100644
> --- a/gwl/processes.scm
> +++ b/gwl/processes.scm
> @@ -197,12 +197,21 @@
>              ((and (? string?) spec)
>               (lookup-package spec))
>              ((and (? valid-package?) pkg)
> +             (set! (package-output pkg) "out")
> +             pkg)
> +            (((? valid-package? pkg) (? string? output))
> +             (set! (package-output pkg) output)
Looking at the code for handling plain packages, that'd probably work,
but it raises more questions.  Like "why is package-ouput a object-
property?" and "wouldn't this break if someone needed two different
outputs of the same package in a process or even anywhere in the
workflow?"