dotfiles - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	git mv bin/upgrade bin/reconfigure	EuAndreh	2023-02-26	1	-82/+0
\|
*	bin/upgrade: Fix call to timeout	EuAndreh	2023-02-26	1	-1/+1
\| \| \| \| \|	The error message was: timeout: impossible d'exécuter la commande « -- »: Aucun fichier ou dossier de ce type
*	bin/upgrade: Restrict upgrade to up-to 2 hours	EuAndreh	2023-02-20	1	-1/+4
\|
*	bin/upgrade: Explicitly define $HOSTNAME	EuAndreh	2023-02-17	1	-1/+3
\|
*	bin/upgrade: Do some ugly ifs to decide what to upgrade	EuAndreh	2023-02-17	1	-4/+15
\|
*	bin/{gc,upgrade}: Fix path to store password	EuAndreh	2022-12-01	1	-1/+1
\|
*	bin/upgrade: Fix path to current Guix Home file	EuAndreh	2022-11-21	1	-1/+1
\| \| \| \|	Follow-up on 7406e924e29f179b2d5aa676c5378866b67ac41c.
*	bin/upgrade: Use the current files for the upgrade	EuAndreh	2022-11-19	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Imagine 2 scenarios: 1. I leave home.scm in an intermediary broken state, and an important security update is available. The "guix pull" command will work, but the security fixes won't be installed, because the home.scm file isn't properly formed. Using the current home.scm file addresses that; 2. a malicious program writes to system.scm, and the upgrade automatically implements any changes present in it. Instead the changes to the system, which require root access, shouldn't be blindly done, and using strictly the existing system.scm addresses that. It doesn't address many other bad things the malicious program can do.
*	Manage the Guix System without using root login	EuAndreh	2022-11-16	1	-1/+1
\|
*	bin/upgrade: Use $XDG_CONFIG_DIR over hard-coding ~/.usr/etc	EuAndreh	2022-10-31	1	-1/+1
\|
*	bin/upgrade: Add equivalent of `update` script	EuAndreh	2022-10-23	1	-0/+66