unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add kakoune
Date: Tue, 10 Jan 2017 17:26:11 -0500	[thread overview]
Message-ID: <20170110222611.GA8431@jasmine> (raw)
In-Reply-To: <87wpehkns6.fsf@zancanaro.id.au>

[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]

On Sat, Dec 31, 2016 at 10:19:53AM +1100, Carlo Zancanaro wrote:
> On Fri, Dec 30 2016, Leo Famulari wrote
> >> diff --git a/gnu/packages/patches/kakoune-fix-bash-path.patch b/gnu/packages/patches/kakoune-fix-bash-path.patch
> >> diff --git a/gnu/packages/patches/kakoune-leave-manpages-uncompressed.patch b/gnu/packages/patches/kakoune-leave-manpages-uncompressed.patch

> > In this case, we need to explain why upstream's approach of finding a
> > POSIX shell doesn't work.
> 
> Perhaps you can give me a hint on this. I've patched it myself because
> the original code uses confstr with _CS_PATH, but within the build
> environment (and presumably outside of it, too) it gives back
> "/bin:/usr/bin". Within the build environment this is invalid (as
> neither directory exists), so the tests all fail. There is a bug[1]
> about this already, but it was closed without fixing the issue (due to
> some complexity/ambiguity in doing so, and no immediate need to fix it).

How about this?

(add-before 'configure 'patch-bash-path
  (lambda* (#:key inputs #:allow-other-keys)
    (substitute* "src/shell_manager.cc"
      (("if \\(m_shell.empty\\(\\)\\)" line)
       (string-append "m_shell = \"" (assoc-ref %build-inputs "bash")
                      "/bin/sh\";\n        " line)))
    #t))

It's crude but it seems to work (the tests pass) and it avoids this
issue:

> > Also, using a patch to get half-way there will cause the source code
> > given by `guix build --source` to be unbuildable, right? So, I think we
> > should find another way to fix whatever is wrong with the shell-finding
> > logic. Perhaps it will require cooperation with the upstream
> > maintainers, I don't know.
> 
> I hadn't thought about the effect this would have on `guix build
> --source`. That's a fairly big problem.

Sorry for the slooooow response!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-01-10 22:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-30  3:43 [PATCH] gnu: Add kakoune Carlo Zancanaro
2016-12-30  4:44 ` Carlo Zancanaro
2016-12-30 19:25   ` Leo Famulari
2016-12-30 23:19     ` Carlo Zancanaro
2017-01-10 22:26       ` Leo Famulari [this message]
2017-01-21  1:49         ` Carlo Zancanaro
2017-01-26 10:20           ` Ludovic Courtès
2017-01-26 12:26             ` Carlo Zancanaro
2017-01-26 20:19               ` Marius Bakke
2017-01-26 21:43                 ` Carlo Zancanaro
2017-01-26 22:09                   ` Marius Bakke
2017-01-26 23:57                     ` Carlo Zancanaro
2017-01-27  0:47                       ` Marius Bakke
2017-01-27 23:00                         ` gzip embedded timestamps Ludovic Courtès

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=20170110222611.GA8431@jasmine \
    --to=leo@famulari.name \
    --cc=carlo@zancanaro.id.au \
    --cc=guix-devel@gnu.org \
    /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).