From: Ricardo Wurmus <rekado@elephly.net>
To: Jone <yeger9@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: A few questions about packages
Date: Wed, 07 Mar 2018 18:01:02 +0100 [thread overview]
Message-ID: <87r2ovlt0x.fsf@elephly.net> (raw)
In-Reply-To: <CAH6o9V9K6Thhe+ybWY9jGWPgRV+=W52rkRuOv+qhABwGPo_bMQ@mail.gmail.com>
Jone <yeger9@gmail.com> writes:
> 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
>
> (Or is it possible to remove a specific package, in "package-version"
> format?)
You can remove all unused packages with “guix gc”. Individual store
items can be removed with “guix gc -d /gnu/store/…”.
“Unused” means that no profile generation refers to the item, so you may
want to delete old profile generations with “guix package -d” first.
> 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?
After building it once from source you won’t have to build it again
until the dependencies to Icecat are modified.
Building Icecat does indeed take a long time. The current version is
52.6.0-gnu1 and should be built by our build farms. When you’re using
the latest version of Guix then you should be able to get a binary as
soon as the build farms have compiled that package. Only if no binary
is available you will have to build it from source.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-03-09 16:48 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 [this message]
2018-03-07 17:38 ` Konrad Hinsen
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=87r2ovlt0x.fsf@elephly.net \
--to=rekado@elephly.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).