unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Jone <yeger9@gmail.com>, help-guix@gnu.org
Subject: Re: A few questions about packages
Date: Wed, 7 Mar 2018 18:38:52 +0100	[thread overview]
Message-ID: <a647be73-c947-117a-7e51-de61e2839ea3@fastmail.net> (raw)
In-Reply-To: <CAH6o9V9K6Thhe+ybWY9jGWPgRV+=W52rkRuOv+qhABwGPo_bMQ@mail.gmail.com>

On 07/03/2018 17:09, Jone wrote:

> Hello. Can I remove old package versions and other builds? On the 
> example of Icecat:
> 
>      252.1 MiB [          ] 
> /5ym67s5vp1vmnc3y4ds4r3687vc3nl25-icecat-52.6.0-gnu1
>      252.0 MiB [          ] 
> /360i9ca4gnm3rsjj8v43ih0j3mfrp40n-icecat-52.6.0-gnu1
>      246.8 MiB [          ] 
> /kd0nnq3i0qarx4vqxcampxfj3igxn84h-icecat-52.3.0-gnu1

"guix gc" will delete all packages that are no longer required. Most 
probably that includes all Icecat installs except for the latest. 
However, if two users on the system have different versions of Icecat 
installed, both will be kept.

> And the next question, is also about Icecat: version 52.6.0 was compiled 
> from source. This is too long. Can I create binary package from this 
> local installation?

In a sense you already have one, stored on your computer. So I guess 
your question is how you can use this binary package on a different 
machine, right? There are two answers to this question:

  1) If the other machine also runs Guix, the answer is "guix archive":
 
https://www.gnu.org/software/guix/manual/guix.html#Invoking-guix-archive

  2) If the other machine does not use Guix, have look at "guix pack":
     https://www.gnu.org/software/guix/manual/guix.html#Invoking-guix-pack

Konrad.

  parent reply	other threads:[~2018-03-07 17:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 16:09 A few questions about packages Jone
2018-03-07 17:01 ` Ricardo Wurmus
2018-03-07 17:38 ` Konrad Hinsen [this message]
2018-03-07 19:26   ` Jone
2018-03-07 20:15     ` Jone
2018-03-07 21:23       ` Ricardo Wurmus
2018-03-11 21:43   ` Jone
2018-03-11 20:59     ` Ricardo Wurmus
2018-03-12  1:41       ` Jone
2018-03-13 19:15     ` Jone
2018-03-13 17:24       ` Björn Höfling
2018-03-13 19:36       ` Jone
2018-03-13 17:25         ` Ricardo Wurmus
2018-03-13 22:32           ` Jone
2018-03-13 22:38             ` Adonay Felipe Nogueira
2018-03-13 17:35         ` Björn Höfling
2018-03-13 22:48           ` Jone
2018-03-13 20:25             ` Björn Höfling
2018-03-10 11:26 ` Jone
2018-03-10 21:38   ` 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=a647be73-c947-117a-7e51-de61e2839ea3@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --cc=help-guix@gnu.org \
    --cc=yeger9@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.
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).