From: Alexei Drozdov <alexei.drozdov@smddev.com>
To: help-guix@gnu.org
Subject: Re: Lazy users and updates
Date: Fri, 27 Dec 2019 17:19:53 +0300 [thread overview]
Message-ID: <CAL0OLYjK+Gfq0Suh7wGgjAaX3nzgcn2jP5kX9QY=y+LSPQ32LA@mail.gmail.com> (raw)
In-Reply-To: <v3kRA08AAdmsZ9LmEStyAJQKFB9z0IqZJWSWsZYfX7x52sQHBIJH55ipOkwlQlWuaE0-N6wwrAZ8JLoopOIOdOkxtL8wvLxT8udKz8vaE1U=@protonmail.com>
It looks like it is not a technical question at all.
Organizational may be.
You can see which packages are obsolete and to remind users to renew them.
пт, 27 дек. 2019 г. в 16:30, Todor Kondić <tk.code@protonmail.com>:
> 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 :)
>
>
>
>
>
>
>
next prev parent reply other threads:[~2019-12-27 14:20 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 [this message]
2019-12-27 14:56 ` Konrad Hinsen
2019-12-28 20:02 ` Efraim Flashner
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='CAL0OLYjK+Gfq0Suh7wGgjAaX3nzgcn2jP5kX9QY=y+LSPQ32LA@mail.gmail.com' \
--to=alexei.drozdov@smddev.com \
--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).