unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: 白い熊@相撲道 <guix-devel_gnu.org@sumou.com>
To: ludo@gnu.org
Cc: GuixSD <guix-devel@gnu.org>
Subject: Re: Libreoffice building (sort of)
Date: Wed, 11 Mar 2015 10:01:41 +0100	[thread overview]
Message-ID: <26d5018175cf3d29bd0f9c99081c4841@hcoop.net> (raw)
In-Reply-To: <87mw3lm3cp.fsf@gnu.org>

On 2015-03-10 13:41, ludo@gnu.org wrote:
> "白い熊 @相撲道" <guix-devel_gnu.org@sumou.com> skribis:
> 
>> wget 
>> http://git.savannah.gnu.org/cgit/guix.git/snapshot/wip-libreoffice.tar.gz
>> guix pull --url=file:///path/to/wip-libreoffice.tar.gz
>> guix package -i libreoffice
>> 
>> It's building now, apparently everything from source, so probably a 
>> long way to go...
>> 
>> Let's see if it will put a unable libreoffice instance in the store...
> 
> Please let us know how it goes.  If it builds and is usable, we should
> merge it.

Well it did build indeed! And now I have a working LibreOffice in the 
store. Tested briefly, works without a hitch so far.

Unrelated, but maybe you could advise me as I'm just starting to study 
Guix deeply:

Have I somehow "poluted" the environment via the pull of the 
wip-libreoffice tar? I'm asking this as I see a different behavior now 
with `guix package -d' and `-i' for other packages now than before, and 
a lot of building from source. Also `# guix gc' will delete as garbage a 
derivation of tar, bzip2, and module-import, and `# guix pull' spends a 
long time building these from source. And thus in a circle.

What can I do about this?
-- 
白い熊@相撲道

  reply	other threads:[~2015-03-11  9:01 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             ` 白い熊@相撲道 [this message]
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
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=26d5018175cf3d29bd0f9c99081c4841@hcoop.net \
    --to=guix-devel_gnu.org@sumou.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).