From: Nils Gillmann <ng0@n0.is>
To: swedebugia <swedebugia@riseup.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Fwd: bug#31907: Acknowledgement (New users get wrong/old profile path to guix after reconfiguring )
Date: Wed, 20 Jun 2018 06:08:00 +0000 [thread overview]
Message-ID: <20180620060800.7x3zowrxhwfs6zbq@abyayala> (raw)
In-Reply-To: <153C7427-EE19-4BDC-AA27-EFA9D630D475@riseup.net>
swedebugia transcribed 5.0K bytes:
> Hi
>
> I just reported this bug.
>
> As a reaction to the recent guix pull update and the people who had a bad experience I have an idea.
>
> We create a new guix command that
> 1) analyze the current users paths and tell them if
> 1.1) they are good and warns them if they are not and propose a solution in a user-friendly way.
> 2) gives them the possibility to scan and inherit a newer guix from another user without having to run guix pull, build a derivation etc.
Wouldn't the two points below be something for a man page? At least they would include a manpage and
a local mail telling you to read more on it if I'd do it.
> 3) (perhaps) educates the users about what happens when they run pull, reconfures, etc. as different users.
> 4) (perhaps) helps them to abuse the symlinks so that e.g. roots profile follow the current user's or vice versa.
>
> This would enable new users to do a sanity check on guix when they don't yet understand the way guix symlinks, store, pulling, etc. works.
>
> This would also save time and bandwidth because you really don't want to run guix pull multiple times as different users considering the time it takes to compile.
>
> What do you think?
Some are a bit vague but in general those are good ideass.
>
> -------- Original Message --------
> From: help-debbugs@gnu.org
> Sent: June 20, 2018 5:20:02 AM GMT+02:00
> To: swedebugia <swedebugia@riseup.net>
> Subject: bug#31907: Acknowledgement (New users get wrong/old profile path to guix after reconfiguring )
>
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> bug-guix@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 31907@debbugs.gnu.org.
>
> Please do not send mail to help-debbugs@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 31907: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31907
> GNU Bug Tracking System
> Contact help-debbugs@gnu.org with problems
>
> --
> Cheers Swedebugia
prev parent reply other threads:[~2018-06-20 6:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <handler.31907.B.152946475925321.ack@debbugs.gnu.org>
2018-06-20 3:41 ` Fwd: bug#31907: Acknowledgement (New users get wrong/old profile path to guix after reconfiguring ) swedebugia
2018-06-20 6:08 ` Nils Gillmann [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180620060800.7x3zowrxhwfs6zbq@abyayala \
--to=ng0@n0.is \
--cc=guix-devel@gnu.org \
--cc=swedebugia@riseup.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.