From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: =?UTF-8?Q?=E2=80=98sudo=E2=80=99?= leaves PATH =?UTF-8?Q?unch?= =?UTF-8?Q?anged=E2=80=A6?= so what? Date: Fri, 18 Jan 2019 21:29:28 +0100 Message-ID: <20190118212928.452ed4e1@scratchpost.org> References: <87y37jwp1p.fsf@gnu.org> <87h8e7h6yd.fsf@elephly.net> <87r2dbv4w0.fsf@gnu.org> <87zhryv3l5.fsf@roquette.mug.biscuolo.net> <87fttqfmnm.fsf@elephly.net> <87d0ouuro2.fsf@roquette.mug.biscuolo.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/42Ay_3N1PjmJceicAT6YEgW"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:39722) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gkaly-00012p-LM for guix-devel@gnu.org; Fri, 18 Jan 2019 15:29:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gkalw-0002X5-OY for guix-devel@gnu.org; Fri, 18 Jan 2019 15:29:50 -0500 Received: from dd26836.kasserver.com ([85.13.145.193]:53508) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gkalu-0002Is-Nm for guix-devel@gnu.org; Fri, 18 Jan 2019 15:29:48 -0500 In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Caleb Ristvedt Cc: guix-devel@gnu.org --Sig_/42Ay_3N1PjmJceicAT6YEgW Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 18 Jan 2019 19:03:18 +0000 Caleb Ristvedt wrote: > To be clear, it's not so much a real problem as an eyesore. 'sudo guix > package ...' and 'sudo guix pull' will operate on root's profile(s) as > expected, but that also means 'sudo guix system reconfigure' will look at > root's profile when deciding whether to say that it's out of date, even > though the guix actually used for reconfiguring may not be out of date. It > pretty much only ever comes up when reconfiguring, but for those like > myself who are worried by messages like that it can be confusing to try to > resolve. There's an environment variable "SUDO_USER" which still contains the name of the original user. We could check SUDO_USER instead of USER if USER=3Droot, otherwise check US= ER. --Sig_/42Ay_3N1PjmJceicAT6YEgW Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlxCNygACgkQ5xo1VCww uqXkzQf/Y+Y1vnx7DXZyLzlsfhbkZoYzZ1SzqqF7lxBDgJlikR36swwu38CdWPHx Ynxd6GfhJv6iqdPllu5VVVqzzw+tL5Mcv8nLSHKqg5J3071wmCTOsPcf9u/iiMGn 0BTSi0Wk/aJK03jLwAzJbLX5E4BABxPOnnp4F4ByoChXMS5l4y2UIWebpgFhQ3Pt Qcd52/ApkzTb+/HP25heZK5CXzhTpkarmiAE+xMo7u2JEwvuKxDvcy5ufWd9+6PV EJ7CW3aPbKbjhr7p8BvMwCmBLWF2OOhcVO+G/mtJnNpRpce50I44LGR3MZJx6NNO 4bN4qg222WKVnG8j7q2Dc64AQ2gBwQ== =jpFR -----END PGP SIGNATURE----- --Sig_/42Ay_3N1PjmJceicAT6YEgW--