From: Vagrant Cascadian <guix-devel@gnu.org>
To: guix-devel@gnu.org
Cc: Philip McGrath <philip@philipmcgrath.com>
Subject: tracking /etc/profile.d/*guix.sh in downstream distributions
Date: Fri, 19 May 2023 15:10:53 -0700 [thread overview]
Message-ID: <87sfbsht02.fsf@wireframe> (raw)
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Philip McGrath recently pointed out that the /etc/profile.d/guix.sh
snippet had not been updating in the Guix packaging for Debian:
https://bugs.debian.org/1036304
(and as bonus complication, was also renamed to zzz-guix.sh)
The reason I never noticed before is because it is actually a manual
process, with this script embedded in the sys_create_init_profile()
function of etc/guix-install.sh ... and thus easy to miss when updating
packaging.
What would be the impact of separating the /etc/profile.d/zzz-guix.sh
into a separate file upstream? Would guix-install.sh need to be adjusted
to guix-install.sh.in so as to embed the contents of this file?
Alternately, maybe guix-install.sh could be updated to optionally output
or generate the zzz-guix.sh file either by passing commandline arguments
or some other conditional mechanism?
For the short term, I will try to update this manually, but would love
to see a longer term option for future releases!
I am somewhat hoping updating /etc/profile.d/zzz-guix.sh would also fix:
https://bugs.debian.org/988260
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2023-05-20 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 22:10 Vagrant Cascadian [this message]
2023-05-20 3:37 ` tracking /etc/profile.d/*guix.sh in downstream distributions Philip McGrath
2023-05-25 0:45 ` Maxim Cournoyer
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=87sfbsht02.fsf@wireframe \
--to=guix-devel@gnu.org \
--cc=philip@philipmcgrath.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).