From: Alex Kost <alezost@gmail.com>
To: myglc2 <myglc2@gmail.com>
Cc: 22981@debbugs.gnu.org
Subject: bug#22981: guix-edit does not find git checkout directory
Date: Sun, 13 Mar 2016 12:38:51 +0300 [thread overview]
Message-ID: <87k2l6yaxg.fsf@gmail.com> (raw)
In-Reply-To: <8737rv2l36.fsf@gmail.com> (myglc2@gmail.com's message of "Sat, 12 Mar 2016 21:00:29 -0500")
myglc2 (2016-03-13 05:00 +0300) wrote:
[...]
> Thank you for this great summary. This list + the post you referenced
> make me feel better that I am taking so long to figure Guix out ;)
>
> OTOH, guix as more state-full than I had hoped ;(
>
> I suggest that you think of it this way: You are running an easter egg
> hunt (I hope this is an OK analogy). You have awesome eggs (No kidding,
> I can attest that the Guix eggs are truly awesome). When the children
> find the eggs they will be truly happy. But the eggs are hard to
> find. If the children don't find the eggs they will not be happy! Worse
> yet, your eggs will be wasted! So ... make it easy for children to find
> your eggs.
I don't know what an "easter egg hunt" is, but I think I get your
analogy.
> You probably already thought of this: Can guix be made easier to use by
> converting some of the state-full guix configuration into guix recipe
> inputs?
Sorry, my knowledge in English language is not enough to understand this
question. Could you explain what "state-full" means?
--
Alex
next prev parent reply other threads:[~2016-03-13 9:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 21:56 bug#22981: guix-edit does not find git checkout directory myglc2
2016-03-11 11:03 ` Alex Kost
2016-03-11 14:45 ` myglc2
2016-03-12 9:15 ` Alex Kost
2016-03-13 2:00 ` myglc2
2016-03-13 9:38 ` Alex Kost [this message]
2016-03-13 15:42 ` myglc2
2016-03-13 22:01 ` Ludovic Courtès
2016-03-14 8:02 ` Alex Kost
2016-03-24 20:02 ` Ludovic Courtès
2016-03-25 1:18 ` 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=87k2l6yaxg.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=22981@debbugs.gnu.org \
--cc=myglc2@gmail.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).