From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id EMQ2BDjJ32X+ZwEAe85BDQ:P1 (envelope-from ) for ; Thu, 29 Feb 2024 01:00:56 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id EMQ2BDjJ32X+ZwEAe85BDQ (envelope-from ) for ; Thu, 29 Feb 2024 01:00:56 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=BzOkz9V5; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1709164855; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=JVRlkI6/wQqPePB0kkLwXEhEsGsEzCteh1c7lZbgL+c=; b=iQjCTlg6AEzlqOwX1fCNtsVaeAA/0n27YupzxLhlwX7JxGZ7N1bo1wqVvlrfGhkH4E2mUi +v/UF4Q2PVSPgZ+Ay50S5fktmcqW4QTSMMfpB3MmwL1UtC0lNTNlrLpUXKR+4BgjsHKX7X 5gRtNC430Jm5kMHxRg0/SwprIhkPvBcbjPmxrZD1ORrBYz1M8djIgN2jsVc0NjuFW+RGH2 fi/Am6cPwe9tEZ4K7MkUvr6ZrbX3tavMV7onodSph6oyhLsPTp3lgKsz/QuPBjdsiICkAh xc4B2TP1k6GM4vYgN8gzOpQB56/u9y6HagWS9FomrZE1iPLy4TQVa+HJsDkmfg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=BzOkz9V5; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1709164855; a=rsa-sha256; cv=none; b=deVNus2ldEoUNmKPUcX5msXKaE9gGpbZQeXzzE0ikfVe87ahPu4n90A6ZMOUkf4caCQnMd BxzhmitnkvwaMM49pR5FEzX7CTckqx2HWAFGVcCX/E5Q4rxNujN5bF7aaVHy379UlB/PH+ B8EYPfOvuNignJe+hasELSexNAXjhELEfonMv/7DZj8jA2gnuC8cMgLkpHmu8T8iRsxZiG iNfn4d029mnHCnEwE9n5Hp9QfGIbfubFc7W5SuINLQCY9co/MspmrNXAMqXZDgurXnEhOR wnV68YBzwUu5oF7HZl7mn7uta1sqB3OwizbIob120ulngGnqnwBrVM5genx0Ag== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id C83115AF7D for ; Thu, 29 Feb 2024 01:00:55 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rfTqN-0006Cx-L9; Wed, 28 Feb 2024 19:00:11 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rfTqL-0006Cf-Ny for guix-devel@gnu.org; Wed, 28 Feb 2024 19:00:09 -0500 Received: from mail-yw1-x1135.google.com ([2607:f8b0:4864:20::1135]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rfTqI-0005og-G3 for guix-devel@gnu.org; Wed, 28 Feb 2024 19:00:09 -0500 Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-608ed07bdc5so3478927b3.3 for ; Wed, 28 Feb 2024 16:00:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709164805; x=1709769605; darn=gnu.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=JVRlkI6/wQqPePB0kkLwXEhEsGsEzCteh1c7lZbgL+c=; b=BzOkz9V5mIqjgQk5It6JABwv8zdkofrx2kVEOseyBdRyiqvxxQBNSgiHlw6Ec9V5N9 VGQkMcfp9pExXdrSC+BJ6PjJAQXjWUfS/iTbrwGT4FM3b3g2BwCX60Qyzt2WLJFcqDm0 c/+Mg8eGKQ9ylY2YWHdbgv/jh65oJwIi2m8DChCxYmW8GLFuTzIDHqkPbPh4jvBeR0vJ /WwsOlAsvSKA7TERc4hrIOEZgyeo9P6bFecaN6gee+peGgvzgzz3aAgNRYmA6TJRzR35 jlc6scmUG90QsY1rC+R24T5E6nV0WEQkpsXYKtyjqOFNPv+kcbiLoEGX1DX/OT9iR3DY Qpzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709164805; x=1709769605; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=JVRlkI6/wQqPePB0kkLwXEhEsGsEzCteh1c7lZbgL+c=; b=d0VQt1MWIJdp9vbClFwIZvNgzVHdAuG3TZq7uqmXxrbFTxlLpM4iTH7fNf3ByVEVmq y8bfixxvmptnWN9ovwn5DPSeXMiDJRUe6rOzyKbVLvQpOhFq1h04duSisejz8UrlfRSw XILH8MJoMWSTNFmwdwnqpsyCNUrg7koV9x6IgMfWXN+RMtUGWN3esGJqTagRZp3CvE4P uAD9fxN4CpjIAu9rSPoVyEztEaunNG39VxcQJXtp5rZ7iomr2lWk+jopkywc/U/y1zpn rWimeeUKnsi8NBuQKfrvE2XI0zxaXAAqpZR7WSI1qGjy6nEf3CmXxXIvz31MKxxHN0sW K/Mw== X-Gm-Message-State: AOJu0Yxhz18zp1M+FBrN8dP+qQXa1Sa6pAd2ebd6wCE9lWgQ6Dr2kHq5 tUxqGr0H+LI6XuHLEpQ5Zn5Arg56eIEigotz398RbgApWD6AwAcOqcLGsNSsuLm49gCgPGIU50U c6uoYhnitvO1oMXZWvIaDmQq3Ya4TAxKk X-Google-Smtp-Source: AGHT+IGip1u5qwIbfwvs8+ptEBhyPCTwSWVeo3NcFbn9a0VBlWZHbAWkhvVL5W+siyDlHoic6MKSaLY1rOrj7HdsxXA= X-Received: by 2002:a25:b316:0:b0:dc7:45d3:ffd0 with SMTP id l22-20020a25b316000000b00dc745d3ffd0mr806073ybj.1.1709164804933; Wed, 28 Feb 2024 16:00:04 -0800 (PST) MIME-Version: 1.0 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Date: Thu, 29 Feb 2024 00:59:53 +0100 Message-ID: Subject: Guix days guix home discussion To: Guix Devel Content-Type: multipart/alternative; boundary="0000000000000f8ae2061279f1af" Received-SPF: pass client-ip=2607:f8b0:4864:20::1135; envelope-from=gboskovits@gmail.com; helo=mail-yw1-x1135.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list 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+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -9.56 X-Spam-Score: -9.56 X-Migadu-Queue-Id: C83115AF7D X-Migadu-Scanner: mx11.migadu.com X-TUID: pdveH2CSwFTo --0000000000000f8ae2061279f1af Content-Type: text/plain; charset="UTF-8" On guix days in the guix home discussion the following observations were made: 1. It is rare that guix home import does the right thing (it is usually removing some startup file customizations, does not seem to arrange to pick up profiles, not even its own). Either we should improve it, or document that it only gives a skeleton configuration and add some guidance on the steps needed to get a working one. 2. The user default profile and the home package profile being separate is causing some issues. It might be enough to document all the special profiles somewhere (which as of now include at least system profile, user profile, pull profile and home profile), but we can also think about a bit more general solution, along the lines of a home service that ensures that a given profile matches the supplied manifest, and have variables for the special profiles. (These could then provide extensions to the shell services which could arrange to pick them up) 3. Sometime on home reconfigure the shell prompt customizations seem to get lost. Sourcing the shell startup file fixes it. I will have to look into this more to file a proper bug report. 4. Creating a guix development environment service would be beneficial, to showcase the possibilities and to simplify onboarding. On top of there could be an additional service that adds emacs integration to this development environment. 5. There was a recommendation to relax the expectations on the home services merged. Right now a lot of people are just writing services for private use. Most probably such a single usecase service would already be beneficial to multiple people. The idea is the following: make it easy for an initial home service to be merged. (Example: do not ask to implement options that the submitter is not using). Then take care that if there is an addition to the service that it really gets merged with what we already have. This needs a bit of up front design, we have to make sure that the services can be extended while maintaining backwards compatibility. --0000000000000f8ae2061279f1af Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On guix days in the guix home discussion the following ob= servations were made:
1. It is rare that guix home import = does the right thing (it is usually removing some startup file customizatio= ns, does not seem to arrange to pick up profiles, not even its own). Either= we should improve it, or document that it only gives a skeleton configurat= ion and add some guidance on the steps needed to get a working one.
2. The user default profile and the home package profile be= ing separate is causing some issues. It might be enough to document all the= special profiles somewhere (which as of now include at least system profil= e, user profile, pull profile and home profile), but we can also think abou= t a bit more general solution, along the lines of a home service that ensur= es that a given profile matches the supplied manifest, and have variables f= or the special profiles. (These could then provide extensions to the shell = services which could arrange to pick them up)
3. Som= etime on home reconfigure the shell prompt customizations seem to get lost.= Sourcing the shell startup file fixes it. I will have to look into this mo= re to file a proper bug report.
4. Creating a guix d= evelopment environment service would be beneficial, to showcase the possibi= lities and to simplify onboarding. On top of there could be an additional s= ervice that adds emacs integration to this development environment.
5. There was a recommendation to relax the expectations on = the home services merged. Right now a lot of people are just writing servic= es for private use. Most probably such a single usecase service would alrea= dy be beneficial to multiple people. The idea is the following: make it eas= y for an initial home service to be merged. (Example: do not ask to impleme= nt options that the submitter is not using). Then take care that if there i= s an addition to the service that it really gets merged with what we alread= y have. This needs a bit of up front design, we have to make sure that the = services can be extended while maintaining backwards compatibility. --0000000000000f8ae2061279f1af--