Oops, and here is the attachment ... On 05/07/2017 at 08:12 myglc2 writes:
> On 05/06/2017 at 09:33 Catonano writes: > >> 2017-05-06 4:07 GMT+02:00 myglc2 <[email protected]>: >> >> On 05/05/2017 at 18:01 Catonano writes: >> >> > 2017-05-03 21:08 GMT+02:00 myglc2 <[email protected]>: >> > >> > On 05/03/2017 at 18:05 Catonano writes: >> > >> > > 2017-05-02 20:58 GMT+02:00 myglc2 <[email protected]>: >> > > >> > > 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' >> > >> > I didn't kknow this one ! >> > >> > - 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 >> > >> > I think you can't modify a package in place. In fact, with guix edit >> > it gets open as ead only >> > >> > As far as I understand, you should clone it locally, edit the copy in >> that clone, build it, install it with ./pre-inst-env in that clone >> > >> > If that's not too pettifogging for you, i could try >> >> Well, the scenario I outlined assumed running from a 'guix git checkout' >> >> No. I don't know how to run the Emacs guix-* commands on a checkout >> >> because I had the impression that you were running that way. But it may >> be overkill for many users and it really might be better to create a >> demo using a 'guix pull' setup. This could focus on using emacs-guix to >> find, build, install, and inspect packages. >> >> That I can do >> >> It could also demonstrate >> editing the system config, reconfiguring the system, creating a user >> manifest and running 'guix package -m user.scm' >> >> That, I'm not sure I can do. I never created a manifest and I never run guix >> pakage - a-file.scm >> >> Would you mind to write done the relevant commands for me ? > > I have attached the user config manifest I am currently using. I apply > it with ... > > guix package -m g1.scm > > ... you can also invoke this using the emacs-guix 'M-x guix' popup, > which might be nicer to show in the demo. > >> I hope someone reading this will suggest such a package ;-) >> >> Right, I'm open to suggestions >> >> > - build the package: 'C-u . b' >> > >> > This one, for example, would require you to run the emacs-guix facilities >> on a local clone and I don't know how to do that >> > >> > I remember Ludo doing this in a footage but I could use a reminder. >> > >> > Thanks again >> >> Right. And I am happy to share my git checkout config with you if that >> would help. >> >> I'm not sure I understand, here. > > I mean that I am running guix from a git checkout. There are a few > different approaches to doing this. I can outline the approach that I > use when you want it. > >> Have you a system configuration that builds a system based on a guix git >> checkout ? >> I can't do that, either. I'd love to see it > > Hmm, I guess I don't know if you running GuixSD or Guix on another > GNU/Linux OS. I was assuming you are running GuixSD and I was referring > to doing ... > > guix system reconfigure sys.scm > > If you are running guix/GNU/Linux then you won't be able to include this > in the demo. > >> But... would you want to first do the 'git pull' based demo? >> >> Yes. The git chheckout could be a second step > > Great, sounds like a good plan > >> Thanks for your help ! > > YW - George
g1.scm
Description: Binary data
