unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: 宋文武 <iyzsong@envs.net>
To: anguriamelone--- via <help-guix@gnu.org>
Cc: anguriamelone@libero.it
Subject: Re: Message by a novice
Date: Sun, 14 May 2023 14:58:34 +0800	[thread overview]
Message-ID: <87sfbzv1ph.fsf@envs.net> (raw)
In-Reply-To: <1588018684.919240.1684002697666@mail1.libero.it> (anguriamelone's message of "Sat, 13 May 2023 20:31:37 +0200 (CEST)")

anguriamelone--- via <help-guix@gnu.org> writes:

> Hi to everyone.
>
> I am a novice in GNU Guix, so far I used Trisquel GN-Linux 9.0.2
> (i686), but at the end of April the support for the i686 version has
> been discontinued.

Hello, while not abandoned, i686 support in Guix is not well maintained.
Which means less packages are available compare to x86_64, and require
more time build (and maybe fixing) packages yourself instead of download
prebuilt ones ('substitutes' in guix terms).


> I would like to know what are the basic command lines corresponding to
> those of Trisquel GNU-Linux below:

I'll give a quick answer, more info can be find in the guix manual and
online videos.

https://guix.gnu.org/en/manual/en/html_node/Package-Management.html#Package-Management
https://guix.gnu.org/en/videos/2020/everyday-use-of-gnu-guix-part-one/

>
> sudo apt update

guix package --upgrade

> sudo apt upgrade

guix pull

> sudo apt install (package name)

guix package --install

> sudo apt remove --purge (package name)

guix package --remove

> sudo apt search (package name)

guix search

> sudo apt autoremove
> sudo apt purge
> sudo apt autoclean
> sudo apt clean

guix package --delete-generations
guix gc

Underhood, it's very different to apt, see the manual for details.

Hope this will help!


  parent reply	other threads:[~2023-05-14  6:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13 18:31 Message by a novice anguriamelone--- via
2023-05-14  6:40 ` Edouard Klein
2023-05-14  6:58 ` 宋文武 [this message]
2023-05-14 12:49   ` Csepp
2023-05-14  7:59 ` (
2023-05-14 14:52 ` Felix Lechner via

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=87sfbzv1ph.fsf@envs.net \
    --to=iyzsong@envs.net \
    --cc=anguriamelone@libero.it \
    --cc=help-guix@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.
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).