From: Timothy Sample <samplet@ngyro.com>
To: Jone <yeger9@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Any questions yet
Date: Wed, 08 May 2019 20:59:29 -0400 [thread overview]
Message-ID: <87ef58sary.fsf@ngyro.com> (raw)
In-Reply-To: <CAH6o9V-=Y+L-+32c62KRfVtc3OX_vH13v_MV6kveRD2GzOOzhw@mail.gmail.com> (Jone's message of "Wed, 8 May 2019 23:21:11 +0000")
Hi Jone,
Jone <yeger9@gmail.com> writes:
> Hello, people! I don't even know exactly what I would like to ask))
> Well, for example: two calls "guix pull" as root and as user - what
> does the first if the root has 0 packages (besides guix itself,
> right?) But how is this related in the future? I still do not
> understand what I do not understand))
I guess I don’t know exactly what I’m answering, then, but I’ll do my
best! :)
Running “guix pull” updates Guix the program which also means updating
the list of package definitions. It does not affect your current
packages – only Guix itself. This means that it does not matter if you
have 0 packages or 100.
Technically speaking, you usually have (at least) two profiles per user.
One is the “user” profile, and it contains all of the packages you’ve
added either using “guix install” or through a manifest. The other is
profile that “guix pull” uses. It only includes a special up-to-date
Guix packages (with all of its dependencies). Usually, the “user”
profile is linked to from “~/.guix-profile”, and the “guix pull” profile
is linked to from “~/.configure/guix/current”.
If you really want to understand these profiles, the manual is your best
bet. For the “user” profile, see “(guix) Invoking guix package”. For
the “guix pull” profile, see “(guix) Invoking guix pull”. Here are
links to these sections on the Web:
<https://www.gnu.org/software/guix/manual/en/html_node/Invoking-guix-package.html>
<https://www.gnu.org/software/guix/manual/en/html_node/Invoking-guix-pull.html>
> I know Scheme/Guile only at the level of a ordinary user, so I ask
> such stupid questions, sorry. And English is so-so)) But I love
> freedom! Thanks.
>
> Yes, and also: I wrote a couple of package definitions for several
> XFCE plugins that are not in the repositories. Is it impossible to
> send somewhere? True, the versions is old..
It is possible! You should update them first, if you can. Then, you
can send them to us as patches via email. It may take some time, but
eventually a friendly reviewer will look at your patches, maybe provide
some suggestions on how to improve them, and finally apply them to Guix.
Again, the Guix manual has a good guide to everything you need to know
to do this. See “(guix) Contributing”, which is on the Web at the
following address:
<https://www.gnu.org/software/guix/manual/en/html_node/Contributing.html#Contributing>
Particularly, check out the last section called “Submitting Patches”.
Hope that helps!
-- Tim
prev parent reply other threads:[~2019-05-09 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 23:21 Any questions yet Jone
2019-05-09 0:59 ` Timothy Sample [this message]
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=87ef58sary.fsf@ngyro.com \
--to=samplet@ngyro.com \
--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).