all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: add lispf4
Date: Thu, 11 Feb 2016 23:00:24 -0500	[thread overview]
Message-ID: <20160212040024.GA29448@jasmine> (raw)
In-Reply-To: <87oaboislg.fsf@grrlz.net>

On Wed, Feb 10, 2016 at 02:48:43PM +0100, Nils Gillmann wrote:
> Leo Famulari <leo@famulari.name> writes:
> 
> > On Tue, Feb 09, 2016 at 11:30:21AM +0100, Nils Gillmann wrote:
> > I'm not sure — did you figure out a solution to the problem with the
> > package?
> 
> Yes and no.
> I am not sure, as I don't know Guix enough currently.
> On Debian, compiled in $HOME I get 644 on SYSATOMS + BASIC.IMG.
> If this is the default, should I just assume for a moment that
> this will be okay to set for (chmod) in the install procedure and
> patch it as such?

I spent some time trying to get this to work without success.

Can you elaborate on your workflow? Are you using the `guix environment`
tool to create a build environment and then building "by hand" by
running `make`, or are you using using `./pre-inst-env guix build`, or
some combination of the two?

The `./pre-inst-env` method [0] should ensure that if a package works for
you, it will work when installed from the master Guix repo.

For example, you could build and test a package like this:
$ ./pre-inst-env guix build lispf4 && ./pre-inst-env guix package -i lispf4

[0]
https://www.gnu.org/software/guix/manual/guix.html#Running-Guix-Before-It-Is-Installed

  reply	other threads:[~2016-02-12  4:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06 18:45 [PATCH] gnu: add lispf4 Nils Gillmann
2016-02-06 22:14 ` Leo Famulari
2016-02-07  0:01   ` Nils Gillmann
2016-02-07 10:59     ` Ricardo Wurmus
2016-02-07 11:09     ` Ricardo Wurmus
2016-02-07 15:09       ` Nils Gillmann
2016-02-18 11:38         ` [PATCH] gnu: add lispf4 (Update) Nils Gillmann
2016-02-18 11:48           ` Ricardo Wurmus
2016-02-07 16:50 ` [PATCH] gnu: add lispf4 Nils Gillmann
2016-02-08  0:36   ` Leo Famulari
2016-02-08 11:17     ` Nils Gillmann
2016-02-08 20:14       ` Leo Famulari
2016-02-09  1:31         ` Nils Gillmann
2016-02-09  7:16           ` Efraim Flashner
2016-02-09 10:30             ` Nils Gillmann
2016-02-10  5:36               ` Leo Famulari
2016-02-10 13:48                 ` Nils Gillmann
2016-02-12  4:00                   ` Leo Famulari [this message]
2016-02-14  3:52             ` Nils Gillmann
2016-02-14  8:10               ` Ricardo Wurmus
2016-02-14 21:31                 ` Nils Gillmann
2016-02-14 21:36                   ` Ricardo Wurmus
2016-02-14  4:05             ` Nils Gillmann

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=20160212040024.GA29448@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=niasterisk@grrlz.net \
    /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.