From: Rodrigo Morales <moralesrodrigo1100@gmail.com>
To: help-guix@gnu.org
Subject: Newbie: Why using "guix edit" opens read-only files in /gnu/store?
Date: Sun, 25 Jun 2023 03:14:06 +0000 [thread overview]
Message-ID: <CAGxMbPbF8OQeWmO8_04wuGq_7aEfHBqq6w93Fp1L-BRYQJpQzQ@mail.gmail.com> (raw)
From what I understand, no file in `/gnu/store' can be edited by any
user. My question is: Isn't the purpose of `guix edit' edit package
definitions? Then, why when `guix edit <<package>>' is executed, a file
under /gnu/store is shown? For the record, I just executed `guix edit
emacs' and the file
/gnu/store/nxy09dxmm23krdgszgww2v80v8bkcll5-guix-module-union/share/guile/site/3.0/gnu/packages/emacs.scm
was opened.
How am I supposed to edit the package definition if it is defined in a
file under `/gnu/store' (read-only file system)?
I might have skipped an important part when reading the documentation. If
so, please point me to that part.
next reply other threads:[~2023-06-25 3:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 3:14 Rodrigo Morales [this message]
2023-06-25 3:50 ` Newbie: Why using "guix edit" opens read-only files in /gnu/store? Vagrant Cascadian
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=CAGxMbPbF8OQeWmO8_04wuGq_7aEfHBqq6w93Fp1L-BRYQJpQzQ@mail.gmail.com \
--to=moralesrodrigo1100@gmail.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).