unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: myglc2 <myglc2@gmail.com>
To: 22587@debbugs.gnu.org
Subject: bug#22587: ‘guix edit’ & ‘M-x guix-edit' typo, rename, & mode change
Date: Sun, 07 Feb 2016 14:22:36 -0500	[thread overview]
Message-ID: <87y4awiav7.fsf@gmail.com> (raw)
In-Reply-To: <8737t4jt1j.fsf@gmail.com>

Andreas Enge <andreas@enge.fr> writes:

> On Sun, Feb 07, 2016 at 01:04:40PM -0500, myglc2 wrote:
>> TYPO:
>> "edit" (last line above) should be replaced with "view", "inspect", or
>> "examine".
>> RENAME:
>> Calling these functions 'guix edit' and 'M-x guix-edit' implies that the
>> user will be able to modify the recipe, but this is not actually the
>> case.
>
> This depends on the user's rights. In a global installation, root is allowed
> to modify. In a git checkout, one would need to do "./pre-inst-env guix edit"
> like with all other guix commands.
>
> Andreas

Of course, running as root, 'guix edit' opens the recipe read-only and
from there, root can do whatever he/she likes.

But, AIUI, this goes against the guix concept of an immutable store.

To describe and name this function to imply that one could/should edit
recipes in the store based on the "corner case" of root having the
ultimable ability to do so seems counter to how you would want to
encourage even a root user to proceed.

  reply	other threads:[~2016-02-07 19:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 18:04 bug#22587: ‘guix edit’ & ‘M-x guix-edit' typo, rename, & mode change myglc2
2016-02-07 18:58 ` Andreas Enge
2016-02-07 19:22   ` myglc2 [this message]
2016-02-07 19:34     ` Andreas Enge
2016-02-07 20:26       ` myglc2
2016-02-08  8:34 ` Alex Kost
2016-02-08 15:30   ` Ludovic Courtès
2016-02-08 18:29   ` myglc2
2016-04-18  8:37     ` Alex Kost
2016-04-18 17:41       ` Ludovic Courtès
2016-04-19  8:18         ` Alex Kost
2016-04-19 10:50           ` Ludovic Courtès
2016-04-20  7:20             ` Alex Kost
2016-04-20 15:31               ` Ludovic Courtès
2016-04-21 10:40                 ` Alex Kost
2016-06-02 19:40                   ` Ludovic Courtès
2016-06-03 19:04                     ` Alex Kost
2016-06-04 11:21                       ` Ludovic Courtès
2016-04-18 21:10       ` myglc2

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=87y4awiav7.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=22587@debbugs.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.
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).