all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: myglc2 <myglc2@gmail.com>
To: Catonano <catonano@gmail.com>
Cc: Alex Kost <alezost@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: is it me ?
Date: Wed, 03 May 2017 15:08:02 -0400	[thread overview]
Message-ID: <86d1bpn4h9.fsf@gmail.com> (raw)
In-Reply-To: <CAJ98PDyCdyL9XGVHYHSHFrpp2UTFgMY5gz9VSb=sJXVnrhuakA@mail.gmail.com> (catonano@gmail.com's message of "Wed, 3 May 2017 18:05:45 +0200")

On 05/03/2017 at 18:05 Catonano writes:

> 2017-05-02 20:58 GMT+02:00 myglc2 <myglc2@gmail.com>:
>
>  As it stands, your video is a great sanity check for someone wondering
>  if their emacs-guix environment is working properly. It is also a great
>  demonstration of how easy it is for a guix user to see and, with a git
>  checkout, modify a package. 
>
>  If you expanded it a bit to illustrate a few
>  more guix-edit/geiser features, it could be a great addition to the
>  guix-video-verse, and, IMO, a good thing to add to www.gnu.or
>
> Which eatures, exactly, you would like to be showed ? 

How about a scenario like this, all done from within emacs-guix running
against a git checkout ...

- find a package

- install it

- observe how it is working

- consider changing a config flag

- 'M-x Guix edit <package>'

- download the source: 'C-u . s'

- copy the package source out of the store (there is probably a better
  thing to do here)

- in <package> source: './configure --help' to see config options

- 'M-x Guix edit <package>' & modify #:configure-flags

- build the package: 'C-u . b'

- install the new version

- verify the package behavior has changed

- commit the change

- produce a potential guix patch

Note: I am not a 'M-x guix-edit' "daily driver". I hope others who are
will comment/improve the outline.

ISTM this scenario is useful because ...

1) it shows the control that guix gives to users

2) a knowledgeable <package> user can follow it to help improve how
   <package> runs in guix.

HTH - George

  reply	other threads:[~2017-05-03 19:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01 11:11 is it me ? Catonano
2017-05-01 16:41 ` myglc2
2017-05-01 21:38 ` Ludovic Courtès
2017-05-02  9:09 ` Alex Kost
2017-05-02 17:37   ` Catonano
2017-05-02 18:58     ` myglc2
2017-05-03 16:05       ` Catonano
2017-05-03 19:08         ` myglc2 [this message]
2017-05-05 13:48           ` Amirouche
2017-05-05 16:01           ` Catonano
2017-05-06  2:07             ` myglc2
2017-05-06  7:33               ` Catonano
2017-05-07 12:12                 ` myglc2
2017-05-07 12:14                   ` myglc2
2017-05-09 16:44                   ` Catonano
2017-05-11 15:21                     ` myglc2
2017-05-14  7:16                       ` Catonano
2017-05-14 13:06                         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86d1bpn4h9.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=alezost@gmail.com \
    --cc=catonano@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.
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.