all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andy Patterson <ajpatter@uwaterloo.ca>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 31548@debbugs.gnu.org
Subject: [bug#31548] [PATCH] gnu: Add sbcl-stumpwm-checkout.
Date: Sun, 17 Jun 2018 17:59:16 -0400	[thread overview]
Message-ID: <20180617175916.3df21a46@uwaterloo.ca> (raw)
In-Reply-To: <87y3fd9zlu.fsf@gmail.com>

Hi Oleg,

On Sun, 17 Jun 2018 18:55:41 +0300
Oleg Pykhalov <go.wigust@gmail.com> wrote:

> Hello Ludovic,
> 
> Apologies for a long reply.
> 
> ludo@gnu.org (Ludovic Courtès) writes:
> 
> […]
> 
> >> In that case, I’d suggest changing the “name” field to
> >> “stumpwm-next” as we did a few times in the past, so that by
> >> default, people still get the official release.  
> 
> Changing “name” field unfortunatelly breaks the build.  I didn't
> investigate a reason yet and I don't want to push without changing
> “name” field because users will install the “stumpwm-next” by default.

I haven't looked much into your patch, but this might be because the
asdf build system uses the package name to guess where the system will
be defined. If the package name differs from the system name, this
behaviour can be overridden using the #:asd-system-name argument.

Hope that helps,

--
Andy

  reply	other threads:[~2018-06-17 22:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22  8:43 [bug#31548] [PATCH] gnu: Add sbcl-stumpwm-checkout Oleg Pykhalov
2018-05-23 13:03 ` Ludovic Courtès
2018-05-25 10:46   ` Oleg Pykhalov
2018-05-25 16:08     ` Ludovic Courtès
2018-06-16 22:08       ` Ludovic Courtès
2018-06-17 15:55         ` Oleg Pykhalov
2018-06-17 21:59           ` Andy Patterson [this message]
2018-06-18 21:39             ` [bug#31548] [PATCH] gnu: sbcl-stumpwm: Update to 18.05 Oleg Pykhalov
2018-06-23 22:20               ` Oleg Pykhalov

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=20180617175916.3df21a46@uwaterloo.ca \
    --to=ajpatter@uwaterloo.ca \
    --cc=31548@debbugs.gnu.org \
    --cc=go.wigust@gmail.com \
    /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.