unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: "help-guix\\@gnu.org" <help-guix@gnu.org>
Subject: Re: Lazy users and updates
Date: Sat, 28 Dec 2019 22:02:34 +0200	[thread overview]
Message-ID: <20191228200234.GT23018@E5400> (raw)
In-Reply-To: <93c355d8-8dac-2670-7b8a-9a5af8f4438b@fastmail.net>

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

On Fri, Dec 27, 2019 at 03:56:07PM +0100, Konrad Hinsen wrote:
> Am 27.12.19 um 14:29 schrieb Todor Kondić:
> 
> > Given the user-centric approach of Guix, it feels like it should be up to individual users of a shared system to deal with installations and the system updates. But, what to do when they are lazy, or too novice for fiddling with the command line?
> > 
> > Do I use the admin's prerogative and set their own crontabs to pull and "package -u" once in a while? I feel like this is overriding their free will for their own good.
> > 
> > Note that the question is ethical, as much as technical :)
> 
> Ask your users what they prefer. I'd want to handle this myself, but many of
> my colleagues would prefer an admin to take care of all updating. We are all
> different :-)
> 

Also note the difference in outputs beween 'guix package
--list-profiles' and 'sudo guix package --list-profiles'

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

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

      reply	other threads:[~2019-12-28 20:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 13:29 Lazy users and updates Todor Kondić
2019-12-27 14:19 ` Alexei Drozdov
2019-12-27 14:56 ` Konrad Hinsen
2019-12-28 20:02   ` Efraim Flashner [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=20191228200234.GT23018@E5400 \
    --to=efraim@flashner.co.il \
    --cc=help-guix@gnu.org \
    --cc=konrad.hinsen@fastmail.net \
    /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).