Re: unexpected reproducibility of reproducible blog post?

result is the same for 86081d9d7f88a7faee6fd14e8a085cb95ac1e36a (a "random" commit in January), as long as you remember to actually use the time-machine to jump back to the commit mentioned in the blog post. > > I don't know, what configuration exactly went into the blog post, > &g

Re: unexpected reproducibility of reproducible blog post?

what configuration exactly went into the blog post, but I > assume, it is not the same as for the time-machine experiments before. > Since the prefix `guix time-machine --channels=guix-version-for- > reproduction.txt --` appears to be missing from the command, that hash > is th

unexpected reproducibility of reproducible blog post?

with some override for gcc- toolchain, things might be different. I don't know, what configuration exactly went into the blog post, but I assume, it is not the same as for the time-machine experiments before. Since the prefix `guix time-machine --channels=guix-version-for- reproduction.txt --` appears

unexpected reproducibility of reproducible blog post?

Dear, Based on the nice blog post [1], instead of really travelling I just travel in time. :-) If I read correctly and if I did not do any mistake, the final hash is not the same now than before. It is not what I was expecting. Expected output (blog post): /gnu/store

Re: [BLOG] rust blog post

On Tue, Nov 26, 2019 at 04:19:01PM -0800, Bengt Richter wrote: > Hi Pierre, and apologies to Efraim... > > On +2019-11-26 14:01:10 +0100, Pierre Neidhardt wrote: > > Bengt Richter writes: > > > > > be a binary. Its... both? Javascript libraries leave distro > > > > Typo: "It's". > > It's

Re: [BLOG] rust blog post

Hi Pierre, and apologies to Efraim... On +2019-11-26 14:01:10 +0100, Pierre Neidhardt wrote: > Bengt Richter writes: > > > be a binary. Its... both? Javascript libraries leave distro > > Typo: "It's". > I noticed that too, but it's Efraim's typo, as is the entire text: I merely

Re: [BLOG] rust blog post

Hi Guix, In case someone likes a narrower style: On +2019-11-26 12:27:37 +0200, Efraim Flashner wrote: > Hopefully this is better. I added a new line between each paragraph > > On Tue, Nov 26, 2019 at 10:58:41AM +0100, Pierre Neidhardt wrote: > > I think the attachment broke the formatting of

Re: [BLOG] rust blog post

Hopefully this is better. I added a new line between each paragraph On Tue, Nov 26, 2019 at 10:58:41AM +0100, Pierre Neidhardt wrote: > I think the attachment broke the formatting of the file (there is no > paragraph break). Could you resend it? > -- Efraim Flashner אפרים פלשנר GPG key =

Re: [BLOG] rust blog post

I think the attachment broke the formatting of the file (there is no paragraph break). Could you resend it? -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

[BLOG] rust blog post

There's one or two FIXMEs and the like in the blog post but I figured I'd send it off anyway. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted It's easy to think of Rust

Re: wip blog post (v2): running Guix System on ARM

Le Sat, 23 Nov 2019 18:19:22 +0100, Ludovic Courtès a écrit : > Hello, > > Danny Milosavljevic skribis: > > > On Sun, 17 Nov 2019 17:57:28 +0100 > > Julien Lepiller wrote: > > > >> Thank you! attached is a new version of that blog post. I think

Re: wip blog post (v2): running Guix System on ARM

Hello, Danny Milosavljevic skribis: > On Sun, 17 Nov 2019 17:57:28 +0100 > Julien Lepiller wrote: > >> Thank you! attached is a new version of that blog post. I think I'll >> convert it to texinfo and add it to the cookbook, instead of making it >> a blog po

Re: wip blog post (v2): running Guix System on ARM

Hi Julien, On Sun, 17 Nov 2019 17:57:28 +0100 Julien Lepiller wrote: > Thank you! attached is a new version of that blog post. I think I'll > convert it to texinfo and add it to the cookbook, instead of making it > a blog post, as we then could change or remove it more easily if

Re: wip blog post: running Guix System on ARM

On Sun, Nov 17, 2019 at 08:43:33PM +0100, Ludovic Courtès wrote: > Hello! > > Julien Lepiller skribis: > > > Hi, attached is a draft for a blog post (or a section in the cookbook) > > for explaining how to install the Guix System on an ARM board. WDYT? > > I rea

Re: wip blog post: running Guix System on ARM

Hello! Julien Lepiller skribis: > Hi, attached is a draft for a blog post (or a section in the cookbook) > for explaining how to install the Guix System on an ARM board. WDYT? I really like it! Nitpick: s/grub/GRUB/ and s/u-?boot/U-Boot/ (when referring to the software). Perhaps a ref

Re: wip blog post: running Guix System on ARM

Hi, Pierre Neidhardt skribis: >> ### The kernel modules >> >> In order for Guix to be able to load the system from the initramfs, it will >> probably need > > Maybe define initramfs? Or just link to > https://en.wikipedia.org/wiki/Initramfs. I’d suggest writing “initial RAM disk (initrd)”

Re: wip blog post: running Guix System on ARM

Hello, Danny Milosavljevic skribis: > On Wed, 13 Nov 2019 22:21:54 +0100 > Julien Lepiller wrote: > >> Hi, attached is a draft for a blog post (or a section in the cookbook) >> for explaining how to install the Guix System on an ARM board. WDYT? > > I guess it can't

Re: wip blog post (v2): running Guix System on ARM

Le Thu, 14 Nov 2019 13:12:11 +0100, Danny Milosavljevic a écrit : > Hi Julien, > > On Wed, 13 Nov 2019 22:21:54 +0100 > Julien Lepiller wrote: > > > Hi, attached is a draft for a blog post (or a section in the > > cookbook) for explaining how to install the Guix

Re: wip blog post: running Guix System on ARM

Le Thu, 14 Nov 2019 12:05:34 +0100, "pelzflorian (Florian Pelz)" a écrit : > On Thu, Nov 14, 2019 at 10:29:22AM +0100, Pierre Neidhardt wrote: > > Neat, thanks for this article! > > > > Yes, thank you! I have not tried yet though. > > Maybe add the top add instructions what to do if

Re: wip blog post: running Guix System on ARM

Hi Julien, On Wed, 13 Nov 2019 22:21:54 +0100 Julien Lepiller wrote: > Hi, attached is a draft for a blog post (or a section in the cookbook) > for explaining how to install the Guix System on an ARM board. WDYT? I guess it can't hurt to describe this stuff as it works now, but th

Re: wip blog post: running Guix System on ARM

On Thu, Nov 14, 2019 at 10:29:22AM +0100, Pierre Neidhardt wrote: > Neat, thanks for this article! > Yes, thank you! I have not tried yet though. Maybe add the top add instructions what to do if installation fails (i.e. flash the SD with another operating system and start anew). > > Make

Re: wip blog post: running Guix System on ARM

Hi, Thank you for the article! I would find interesting to point somewhere in your post to these previous blog posts [1] [2] [3] about ARM and Guix. :-) [1] https://guix.gnu.org/blog/2017/porting-guixsd-to-armv7/ [2] http://guix.gnu.org/blog/2018/guix-on-android/ [3]

Re: wip blog post: running Guix System on ARM

Hi Julien, Julien Lepiller writes: > Hi, attached is a draft for a blog post (or a section in the cookbook) > for explaining how to install the Guix System on an ARM board. WDYT? LOL! \O/ This should be a cookbook section, and released soon unless other people find some error or imp

wip blog post: running Guix System on ARM

Hi, attached is a draft for a blog post (or a section in the cookbook) for explaining how to install the Guix System on an ARM board. WDYT? Guix on an ARM Board Increasingly people discovering Guix want to try it on an ARM board, instead of their x86 computer. There might

Re: Blog post on documentation video creation

Bonjour Ludo (and Guix :)) > Thank you, Laura! No, thank you for encouraging me to give the talk and publish my post :) Regards :) Laura

Re: Blog post about GSoC project on Cuirass

Indeed! One thing: the links at the bottom, "Cuirass" and "final report" (which should probably be capitalized), are broken. -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

Re: my latest blog post [everyone, please take a cooldown break]

Hi On June 10, 2018 4:37:17 PM GMT+02:00, Kei Kebreau wrote: >Gábor Boskovits writes: > >> +1 >> >> 2018-06-10 15:33 GMT+02:00 Christopher Lemmer Webber >: >> >> Nils Gillmann writes: >> >> > Hi, >> > >> > I think it would be best if everyone involved would cool down for >a couple of >> >

Re: my latest blog post

Catonano skribis: > I just want to record the sorry state of this community You and I both know this community, having interacted on-line for a while and having met in person as well. Like you wrote in the first part of your blog post, the state of this community is anything but sad. I f

Re: my latest blog post

Hi Catonano, Catonano skribis: > you chose to enfforce only some violations, not all of them This is a channel of the Guix project, and our code of conduct applies on this channel (the other issue you referred to was on the Guile channel and is not related to Guix.) The insults and derogatory

Re: my latest blog post [everyone, please take a cooldown break]

Gábor Boskovits writes: > +1 > > 2018-06-10 15:33 GMT+02:00 Christopher Lemmer Webber : > > Nils Gillmann writes: > > > Hi, > > > > I think it would be best if everyone involved would cool down for a couple > of > > days, restructure their thoughts and reflect on this thread. Look at what

Re: my latest blog post [everyone, please take a cooldown break]

+1 2018-06-10 15:33 GMT+02:00 Christopher Lemmer Webber : > Nils Gillmann writes: > > > Hi, > > > > I think it would be best if everyone involved would cool down for a > couple of > > days, restructure their thoughts and reflect on this thread. Look at what > > they are doing, and at how they

Re: my latest blog post [everyone, please take a cooldown break]

Nils Gillmann writes: > Hi, > > I think it would be best if everyone involved would cool down for a couple of > days, restructure their thoughts and reflect on this thread. Look at what > they are doing, and at how they are reacting to other peoples reaction. > This topic is getting quiet heated,

Re: my latest blog post

isconstrued in a similar fashion. >> With regards to the shouting match on #guile that you linked in your >> blog post, I can only say that I would have likely stepped in had this >> happened when I was around. Textual communication certainly should not >> reach these l

Re: my latest blog post

On Sun, Jun 10, 2018 at 11:07:21AM +0200, Catonano wrote: >I'm glad I'm flushing out, people >You are expressing all your jerkiness in all its glory :-) It is obvious by now that this person is trolling. Is there any reason to listen to them? Pj.

Re: my latest blog post

Catonano writes: > Now, please, tell me: is it worth that I edit the manual to include in > a reasonable way the notions that you provided my with about macro > stepping ? > > Or would you refuse to merge it ? My position is that the manual is not an appropriate place to document wishlist items

Re: my latest blog post

Catonano writes: > By the way, a third person wrote me in private right now telling that > Mark was an asshole to them too and they stopped contributing to guix > altogether > > They made a conduct report but nothing happened, eventually they had > to talk to Ludo directly If you're accusing me

Re: my latest blog post

Catonano writes: > 2018-06-10 11:29 GMT+02:00 Ricardo Wurmus : > >> >> Catonano writes: >> >> > They made a conduct report but nothing happened, eventually they had to >> > talk to Ludo directly >> >> From the Code of Conduct: >> >>Instances of abusive, harassing, or otherwise

Re: my latest blog post

2018-06-10 11:29 GMT+02:00 Ricardo Wurmus : > > Catonano writes: > > > They made a conduct report but nothing happened, eventually they had to > > talk to Ludo directly > > From the Code of Conduct: > >Instances of abusive, harassing, or otherwise unacceptable behavior >may be reported

Re: my latest blog post

Catonano writes: > They made a conduct report but nothing happened, eventually they had to > talk to Ludo directly >From the Code of Conduct: Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at

Re: my latest blog post

2018-06-10 11:26 GMT+02:00 Ricardo Wurmus : > > Catonano, > > this language is not at all acceptable anywhere on Guix as you can see > by referencing the Code of Conduct. > > --8<---cut here---start->8--- > Examples of unacceptable behavior by participants

Re: my latest blog post

Catonano, this language is not at all acceptable anywhere on Guix as you can see by referencing the Code of Conduct. --8<---cut here---start->8--- Examples of unacceptable behavior by participants include: * The use of sexualized language or imagery and

Re: my latest blog post

2018-06-10 8:55 GMT+02:00 Pjotr Prins : > On Sat, Jun 09, 2018 at 08:51:59PM -0400, Mark H Weaver wrote: > > myg...@gmail.com writes: > > > Thank you for taking the time to contribute your thoughts. I am sorry > to > > > see you getting so beat up by the responses. Unfortunately the > > >

Re: my latest blog post [everyone, please take a cooldown break]

Hi, I think it would be best if everyone involved would cool down for a couple of days, restructure their thoughts and reflect on this thread. Look at what they are doing, and at how they are reacting to other peoples reaction. This topic is getting quiet heated, and other than the maintainers we

Re: my latest blog post

2018-06-10 0:49 GMT+02:00 : > On 06/07/2018 at 17:25 Catonano writes: > > > I just published my latest blog post > > > > In this post I discuss Guix > > > > And I discuss Guile too > > > > I understand that the language is strong and I expect so

Re: my latest blog post

2018-06-10 2:51 GMT+02:00 Mark H Weaver : > myg...@gmail.com writes: > > > Are there any other acceptable responses, in your view? > I already proposed a way forward and I even asked you if you would refuse to merge it I see you attitute towards that, now. Also: yesterday night, before

Re: my latest blog post

On Sat, Jun 09, 2018 at 08:51:59PM -0400, Mark H Weaver wrote: > myg...@gmail.com writes: > > Thank you for taking the time to contribute your thoughts. I am sorry to > > see you getting so beat up by the responses. Unfortunately the > > nit-picking of criticisms and the "we are busy, why don't

Re: my latest blog post

myg...@gmail.com writes: > On 06/07/2018 at 17:25 Catonano writes: > >> I just published my latest blog post >> >> In this post I discuss Guix >> >> And I discuss Guile too >> >> I understand that the language is strong and I expect someone to b

Re: my latest blog post

On 06/07/2018 at 17:25 Catonano writes: > I just published my latest blog post > > In this post I discuss Guix > > And I discuss Guile too > > I understand that the language is strong and I expect someone to be upset > > But I feel this is due

Re: my latest blog post

Catonano writes: > Instead of calling me an hopeless moron unwilling to learn, he went and > updated Skribilo, without saying a single word > > I noticed > > And I appreciated it > > So, yes, it was aggressie indeed > > Again. I'll try to be more complete later I think it's great that Ludovic

Re: my latest blog post

Ricardo Wurmus writes: > Catonano writes: > > I wrote this: > >But please do not demand of others to explain everything in detail. >(I’m directing this at everyone who heeds my advice to go to >guile-devel, not at any one person in particular.) > > Rephrasing: I’d like to point this

Re: my latest blog post

't (not immediately is not a fair answer either > > > > Because it's equivalent to a "fuck you" > > Wow. No. > > I think that’s an *extremely* uncharitable reading of what I wrote. I > will refrain from further comments in this thread lest what I write will > be m

Re: my latest blog post

Ricardo, you are right that in my last interaction there was some animosity and the message was below the standard I apologize I see that you are maing an effort to deescalate. I appeciate that. Really I also see that you are suggesting some techical remediation about the store monad And that

Re: my latest blog post

Catonano writes: > Assuming that users read academic articles about programming languages in > order to know your way aroung Guile is not reasonable I fail to see how this follows from Guile’s lack of a macro stepper. To be honest, I never even heard of a macro stepper before. And I have

Re: my latest blog post

Hi Catonano, > 2018-06-09 12:39 GMT+02:00 Ricardo Wurmus : > >> >> Catonano writes: >> >> > Assuming that users read academic articles about programming languages in >> > order to know your way aroung Guile is not reasonable >> >> I fail to see how this follows from Guile’s lack of a macro

Re: my latest blog post

2018-06-09 12:39 GMT+02:00 Ricardo Wurmus : > > Catonano writes: > > > Assuming that users read academic articles about programming languages in > > order to know your way aroung Guile is not reasonable > > I fail to see how this follows from Guile’s lack of a macro stepper. Then you were not

Re: my latest blog post

hen it wasn't Someone else made me notice this too I'll apologize to you too But if you take a look at thhe guile-user mailing list, and another loo at the guix-dev mailing list (or even to the guix help mailing list) you'll get 2 completely different outlooks Maybe it's not aggression Still

Re: my latest blog post

Mark, thank you again for your remarks 2018-06-08 20:05 GMT+02:00 Mark H Weaver : > Hi Catonano, > > Thank you for your email. I don't have time to make a proper response > yet, but for now I will respond to just one point: > > Catonano writes: > > On my side, I was a bit adversary because I

Re: my latest blog post

2018-06-08 15:49 GMT+02:00 Ludovic Courtès : > Hello! > > Catonano skribis: > > > In this post I discuss Guix > > > > And I discuss Guile too > > > > I understand that the language is strong and I expect someone to be upset > > > > But I feel this is due > > > > Happy reading > > > >

Re: my latest blog post

Fis Trivial writes: > time. Little off topic, what I want to say is that, if I didn't tried to > evaluate any code from string, how come a modern interpreter can tell me > the error is happened in "unknown file" "unknown line"? Especially the > "unknown file". I cannot answer this without

Re: my latest blog post

feel very uncomfortable if my replying to some (but not all) emails would be construed as an act of aggression, or really any kind of silent attempt at communicating something. In that case I’d much rather *not* respond to any emails. With regards to the shouting match on #guile that you linked

Re: my latest blog post

Hello! Catonano skribis: > In this post I discuss Guix > > And I discuss Guile too > > I understand that the language is strong and I expect someone to be upset > > But I feel this is due > > Happy reading > > http://catonano.v22018025836661967.nicesrv.de/the-gnu-community.html Thanks for

Re: my latest blog post

> > Fis claimed that the error messages that Guile provides them with don't > include indications about in which file the error occurred > > So he's using Chez scheme instead of Guile, if I remember correctly > > I take from this that the Chez scheme error mesages are better. > Actually, I tried

Re: my latest blog post

Le 2018-06-08 11:34, Clément Lassieur a écrit : Hi Julien, Julien Lepiller writes: I read you're having trouble to find information from the section titles. Info manuals have an index where it's easier to find things. But actually, what helps me the most is to ignore the `info` command

Re: my latest blog post

2018-06-08 11:39 GMT+02:00 Nils Gillmann : > Just my brief encouragement: > > I'm not sure how active the Guile documentation writer(s) are, but if you > know how to write it or initially draft something that would be great. > Writing the code is good, but documenting it affects much more people

Re: my latest blog post

Catonano transcribed 7.7K bytes: > Mark, > > 2018-06-07 19:03 GMT+02:00 Mark H Weaver : > > I appreciate you sharing your thoughts on this. I wanted to apologize > > for making you feel badly; it honestly was not my intent to shame you in > > any way. > > > > Thank you for your kind and

Re: my latest blog post

Hi Julien, Julien Lepiller writes: > I read you're having trouble to find information from the section titles. Info > manuals > have an index where it's easier to find things. But actually, what helps me > the most > is to ignore the `info` command and open either the full .texi source or the >

Re: my latest blog post

Le 2018-06-07 17:25, Catonano a écrit : I just published my latest blog post In this post I discuss Guix And I discuss Guile too I understand that the language is strong and I expect someone to be upset But I feel this is due Happy reading http://catonano.v22018025836661967.nicesrv.de

Re: my latest blog post

2018-06-08 6:24 GMT+02:00 Christopher Lemmer Webber : > I think Catonano and Mark discussed things nicely earlier in the thread, > so I'm not going to weigh in on that (though I do agree that we would > can and should do better, but that also it's important to realize that > community members

Re: my latest blog post

Christopher Lemmer Webber writes: > I think Catonano and Mark discussed things nicely earlier in the thread, > so I'm not going to weigh in on that (though I do agree that we would > can and should do better, but that also it's important to realize that > community members only have so many

Re: my latest blog post

I think Catonano and Mark discussed things nicely earlier in the thread, so I'm not going to weigh in on that (though I do agree that we would can and should do better, but that also it's important to realize that community members only have so many personal resources to be able to respond

Re: my latest blog post

Hello Catonano, Catonano writes: > I just published my latest blog post > > In this post I discuss Guix > > And I discuss Guile too > > I understand that the language is strong and I expect someone to be upset > > But I feel this is due > > Happy reading >

Re: my latest blog post

Mark, 2018-06-07 19:03 GMT+02:00 Mark H Weaver : I appreciate you sharing your thoughts on this. I wanted to apologize > for making you feel badly; it honestly was not my intent to shame you in > any way. > Thank you for your kind and measured words I appreciate both the tone and the content

Re: my latest blog post

On 07.06.2018 17:25, Catonano wrote: http://catonano.v22018025836661967.nicesrv.de/the-gnu-community.html You imply that GNU groups are full of "smug jerk"s, say that "Guile is the realm of smugness and elitarism" and made statements like "The G-golf project is a tiny dot in the universe.

Re: my latest blog post

Hi Catonano, Catonano writes: > I just published my latest blog post > > In this post I discuss Guix > > And I discuss Guile too > > I understand that the language is strong and I expect someone to be upset > > But I feel this is due > > Happy reading >

Re: my latest blog post

Catonano writes: > I just published my latest blog post > > In this post I discuss Guix > > And I discuss Guile too > > I understand that the language is strong and I expect someone to be upset > > But I feel this is due > > Happy reading > > http://catonan

my latest blog post

I just published my latest blog post In this post I discuss Guix And I discuss Guile too I understand that the language is strong and I expect someone to be upset But I feel this is due Happy reading http://catonano.v22018025836661967.nicesrv.de/the-gnu-community.html

Re: Guix on android blog post

Pjotr Prins transcribed 495 bytes: > On Tue, Apr 24, 2018 at 05:12:34PM +0530, Pierre Neidhardt wrote: > > This is gold!! Thanks so much for sharing. > > Totally agree. Great work Julien a.o. Praphrasing one of the greats: > what works on large systems tends to work on small. With minimized >

Re: Guix on android blog post

On Tue, Apr 24, 2018 at 05:12:34PM +0530, Pierre Neidhardt wrote: > Out of curiousity, any model you'd recommend, steered towards > Guix-friendliness? > I don’t have a smartphone myself yet, but I wonder how Purism’s Librem 5 will do once it is released in January. Regards, Florian

Re: Guix on android blog post

On Tue, Apr 24, 2018 at 05:12:34PM +0530, Pierre Neidhardt wrote: > This is gold!! Thanks so much for sharing. Totally agree. Great work Julien a.o. Praphrasing one of the greats: what works on large systems tends to work on small. With minimized size packages Guix is quite ready to take on

Re: Guix on android blog post

Le 2018-04-24 17:02, Ricardo Wurmus a écrit : julien lepiller writes: I would recommend getting an armv7 or x86 device, because packages will be more available than for aarch64 as with my current phone. Is this still a problem? We have two aarch64 build nodes (of

Re: Guix on android blog post

julien lepiller writes: > I would > recommend getting an armv7 or x86 device, because packages will be more > available than for aarch64 as with my current phone. Is this still a problem? We have two aarch64 build nodes (of which one was added very recently), which I’d

Re: Guix on android blog post

2018-04-24T17:12:34+0530 Pierre Neidhardt wrote: > This is gold!! Thanks so much for sharing. Indeed it is! :D > Out of curiousity, any model you'd recommend, steered towards > Guix-friendliness? I would actually ask Replicant project, and potentially help with freeing/liberating the wireless

Re: Guix on android blog post

Le 2018-04-24 13:42, Pierre Neidhardt a écrit : This is gold!! Thanks so much for sharing. This might be the last missing piece before I finally get decided to buy a smartphone for myself:) Out of curiousity, any model you'd recommend, steered towards Guix-friendliness? -- Pierre

Re: Guix on android blog post

This is gold!! Thanks so much for sharing. This might be the last missing piece before I finally get decided to buy a smartphone for myself:) Out of curiousity, any model you'd recommend, steered towards Guix-friendliness? -- Pierre Neidhardt signature.asc Description: PGP signature

Guix on android blog post

Hi Guix! Ludo just published my blog post about running Guix on Android on our website: https://www.gnu.org/software/guix/blog/2018/guix-on-android/. That's a very nice example of how independent our packages are from the platform they run on! It's far from perfect, but feel free to share any

Re: a blog post

Catonano writes: > I posted a brand new post in my little personal somewhat indie blog Thank you for sharing it! > I remember Ludo saying that not only new packages and services would > be needed for the future of Guix but also community oriented stuff > such as blog posts

Re: a blog post

2018-04-07 11:53 GMT+02:00 Hartmut Goebel : > Am 06.04.2018 um 10:58 schrieb Catonano: > > It's about Guix, Guile and Free Software in general. From my very own > > point of view > > Quote: > > [org.mode…] as far as I understand some Google employees worked on

Re: a blog post

by getting employed by Gugle? Is Gugle a magic guild? Who knows? Who cares? I wonder why you think this an appropriate reply to a blog post that clearly implies neither, and how it will influence people still considering writing about Guix. Kind regards, T G-R Sent from a Web browser

Re: a blog post

Am 06.04.2018 um 10:58 schrieb Catonano: > It's about Guix, Guile and Free Software in general. From my very own > point of view Quote: [org.mode…] as far as I understand some Google employees worked on it. Does one become blessed and enlightened by getting employed by Gugle? Is Gugle a

Re: a blog post

Hello Catonano, Thanks for the blog post, I added your feed to my feed reader. I understand your frustration with autotools, it can be difficult to figure out how to get autotools to do what you want. The benefit of autotools is that it creates the same interface to build, test, and install GNU

Autotools formely: a blog post

Hi Catano, Thanks for the blog. Indeed, I love working with Guix and developing with Guix. Guix takes care of my deployment and configuration requirements. I have written some time in the past that with Guix you don't need autotools. The main thing autotools solve is configuring the build for

a blog post

Hello fellow guixers, I posted a brand new post in my little personal somewhat indie blog It's about Guix, Guile and Free Software in general. From my very own point of view You can find it here http://catonano.v22018025836661967.nicesrv.de/guile-and-free-software.html There's also a feed,

<    1   2