unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Jay Sulzberger <jays@panix.com>, help-guix <help-guix@gnu.org>
Subject: Re: What is the standard way to install a package so that all users may use the package?
Date: Mon, 16 Mar 2020 10:15:40 -0700	[thread overview]
Message-ID: <8736a85igz.fsf@ponder> (raw)
In-Reply-To: <Pine.NEB.4.64.2003161013520.10511@panix2.panix.com>

[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]

On 2020-03-16, Jay Sulzberger wrote:
> I run mostly Debian and Debian derived systems.  One week ago I
> installed Guix OS on a Thinkpad laptop.  The install was smooth.
> Then I, as root, installed Emacs.  Of course, my regular non-root
> user "jays", saw no Emacs.  I then, by some command of
> symlinking, got Emacs visible to jays, indeed, the same
> executable of Emacs is now used by both root and jays.
>
> What is the standard way to install a Guix package so that all
> users on a single hardware box, can use the package?  That is,
> I'd like an install procedure so that by means of the procedure,
> installation of a package is like, from one angle of view, just
> using apt on a Debian system.

You would install it as part of the system configuration
(e.g. config.scm) and then run:

  guix system reconfigure /path/to/config.scm

Recent versions of guix system will include the previously used
config.scm and you can use that as a file to tweak:

  guix system list-generations

  Generation 12   Mar 15 2020 16:45:17    (current)
    file name: /var/guix/profiles/system-12-link
    ...
    configuration file: /gnu/store/...-configuration.scm

  cp /gnu/store/...-configuration.scm ~/config.scm

Edit that file to include the listed packages you want available for all
users and off you go.

Also a good idea to maintain this file in revision control, so you can
keep track of changes over time.


That said, each individual user being able to select their own software
is one of the great features of guix, though it takes a bit getting used
to the different workflow. It's generally recommended to keep the system
configuration small; to each their own, though. :)


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2020-03-16 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 14:30 What is the standard way to install a package so that all users may use the package? Jay Sulzberger
2020-03-16 17:15 ` Vagrant Cascadian [this message]
2020-03-16 23:46   ` Jay Sulzberger

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=8736a85igz.fsf@ponder \
    --to=vagrant@debian.org \
    --cc=help-guix@gnu.org \
    --cc=jays@panix.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).