all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Olivier Dion <olivier.dion@polymtl.ca>, gwl-devel@gnu.org
Subject: Re: GWL 0.5 fails with plain packages
Date: Sat, 30 Jul 2022 19:04:06 +0200	[thread overview]
Message-ID: <e6274f5cbb368fd291b09c8a18fd6bff1ffa703f.camel@ist.tugraz.at> (raw)
In-Reply-To: <d54930df8dbfbe6ad7f3da3b1ff1f472df6a36f8.camel@ist.tugraz.at>

Am Samstag, dem 30.07.2022 um 19:03 +0200 schrieb 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
s/plain packages/package specs/ of course


  reply	other threads:[~2022-07-30 17:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 11:45 GWL 0.5 fails with plain packages Liliana Marie Prikler
2022-07-29 15:40 ` Olivier Dion via
2022-07-30 17:03   ` Liliana Marie Prikler
2022-07-30 17:04     ` Liliana Marie Prikler [this message]
2022-07-30 18:47     ` Olivier Dion via
2022-07-31  8:16       ` Liliana Marie Prikler
2022-07-31 13:33         ` Olivier Dion via
2022-07-31 14:35           ` Olivier Dion via
2022-07-31 21:17             ` Olivier Dion via
2022-08-01  7:21               ` Liliana Marie Prikler

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=e6274f5cbb368fd291b09c8a18fd6bff1ffa703f.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=gwl-devel@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    /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.