unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: 白い熊@相撲道 <guix-devel_gnu.org@sumou.com>
Cc: GuixSD <guix-devel@gnu.org>
Subject: Re: Libreoffice building (sort of)
Date: Thu, 12 Mar 2015 19:10:17 -0400	[thread overview]
Message-ID: <877fulzuau.fsf@netris.org> (raw)
In-Reply-To: <1087a716208a8189144690eb294adac7@hcoop.net> ("白い熊@相撲道"'s message of "Thu, 12 Mar 2015 23:56:07 +0100")

白い熊@相撲道 <guix-devel_gnu.org@sumou.com> writes:

> On 2015-03-11 20:17, Mark H Weaver wrote:
>> When you run "/path/to/git/checkout/pre-inst-env guix ..." then it will
>> always use the package descriptions from the git checkout.  This is
>> what
>> I *always* do.  In fact, to make this easier, I put this script in
>> ~/bin/guix:
>>
>> --8<---------------cut here---------------start------------->8---
>> #!/bin/sh
>>
>> exec /home/mhw/guix/pre-inst-env guix "$@"
>> --8<---------------cut here---------------end--------------->8---
>>
>> Also note that when 'pre-inst-env' is used,
>> $HOME/.config/guix/latest is
>> always ignored, so anything you've done with 'guix pull' is irrelevant.
>
> So, if I understand correctly, I'd make the git version, but not make
> install it. Then running `pre-inst-env guix' this will use definitions
> from the git pull...

Yes, that's right.

> What about the store? Should I configure it with --localstatedir set
> to /var when building the git version?

Indeed, that is important.  You'll also need to pass
--with-libgcrypt-prefix=$(guix build libgcrypt | head -1)

      Mark

  reply	other threads:[~2015-03-12 23:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 21:24 9x15bold xfont 白い熊 @相撲道
2015-03-09 22:03 ` Andreas Enge
2015-03-09 23:57   ` 白い熊 @相撲道
2015-03-10  2:29     ` 宋文武
2015-03-10  8:54       ` Libreoffice building (sort of) 白い熊 @相撲道
2015-03-10 12:06         ` 白い熊 @相撲道
2015-03-10 12:41           ` Ludovic Courtès
2015-03-11  9:01             ` 白い熊@相撲道
2015-03-11  9:27               ` 白い熊@相撲道
2015-03-11 12:04                 ` Andreas Enge
2015-03-11 12:34                   ` 白い熊@相撲道
2015-03-12  9:22                   ` Ludovic Courtès
2015-03-11 16:34               ` Mark H Weaver
2015-03-11 17:32                 ` 白い熊@相撲道
2015-03-11 19:17                   ` Mark H Weaver
2015-03-12 22:56                     ` 白い熊@相撲道
2015-03-12 23:10                       ` Mark H Weaver [this message]
2015-03-12  9:25               ` Merging wip-libreoffice Ludovic Courtès
2015-03-12  9:47                 ` Andreas Enge
2015-03-12 14:18                   ` Ludovic Courtès
2015-03-10 12:40       ` 9x15bold xfont Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2014-11-24 17:19 Libreoffice building (sort of) John Darrington
2014-11-24 18:03 ` Ludovic Courtès
2014-11-24 19:07   ` John Darrington

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=877fulzuau.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=guix-devel_gnu.org@sumou.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 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).