Re: Publishing an Official Statement on Self-Hosted Compilers

2016-05-21 Thread Alex Griffin
On Thu, May 12, 2016, at 05:05 AM, Ludovic Courtès wrote: > I like it. :-) > > I think the bit about the “trusting trust” attack should go under “The > Problem”. [...] > > WDYT? > > We should then discuss it with the repro-builds folks, and probably > contact a bunch of compiler writers to get

Re: Publishing an Official Statement on Self-Hosted Compilers

2016-05-14 Thread Ludovic Courtès
Hi! Alex Griffin skribis: > I've put my initial notes in a git repository > [here](https://gitlab.com/ajgrf/bootstrapping-compilers/blob/master/notes.org). > They are in a very rough state, but mostly everything is there in some > form. If anyone has any thoughts please let me

Re: Publishing an Official Statement on Self-Hosted Compilers

2016-05-14 Thread Ludovic Courtès
Hi! Alex Griffin skribis: > I've put my initial notes in a git repository > [here](https://gitlab.com/ajgrf/bootstrapping-compilers/blob/master/notes.org). > They are in a very rough state, but mostly everything is there in some > form. If anyone has any thoughts please let me

Re: Publishing an Official Statement on Self-Hosted Compilers

2016-05-09 Thread Alex Griffin
I've put my initial notes in a git repository [here](https://gitlab.com/ajgrf/bootstrapping-compilers/blob/master/notes.org). They are in a very rough state, but mostly everything is there in some form. If anyone has any thoughts please let me know! Also, if you want to contribute changes you can

Re: Publishing an Official Statement on Self-Hosted Compilers

2016-05-09 Thread Ludovic Courtès
Alex Griffin skribis: > On Fri, May 6, 2016, at 05:09 AM, Ludovic Courtès wrote: >> I think it’s a good idea! A lot of the work to fix this issue will be >> to raise awareness among compiler writers and invite them to have a >> bootstrapping story like you describe. >> >> Other

Re: Publishing an Official Statement on Self-Hosted Compilers

2016-05-06 Thread Alex Griffin
On Fri, May 6, 2016, at 05:09 AM, Ludovic Courtès wrote: > I think it’s a good idea! A lot of the work to fix this issue will be > to raise awareness among compiler writers and invite them to have a > bootstrapping story like you describe. > > Other people in the reproducible-builds community

Re: Publishing an Official Statement on Self-Hosted Compilers

2016-05-06 Thread Ludovic Courtès
Hello! Alex Griffin skribis: > One thing I think the Guix project should do is work with the > reproducible builds folks to publish a document explaining the issues > involved with self-hosted compilers. It should encourage language > communities to continuously maintain some

Re: Publishing an Official Statement on Self-Hosted Compilers

2016-05-06 Thread John Darrington
On Thu, May 05, 2016 at 09:52:32AM -0500, Alex Griffin wrote: Hello Guixlings, One thing I think the Guix project should do is work with the reproducible builds folks to publish a document explaining the issues involved with self-hosted compilers. It should encourage

Re: Publishing an Official Statement on Self-Hosted Compilers

2016-05-06 Thread Pjotr Prins
Reproducible builds of D compilers http://forum.dlang.org/post/fsmdaethvbvcxnunb...@forum.dlang.org On Fri, May 06, 2016 at 01:30:18AM +0300, Efraim Flashner wrote: > On Thu, May 05, 2016 at 09:52:32AM -0500, Alex Griffin wrote: > > Hello Guixlings, > > > > One thing I think the Guix project

Re: Publishing an Official Statement on Self-Hosted Compilers

2016-05-05 Thread Efraim Flashner
On Thu, May 05, 2016 at 09:52:32AM -0500, Alex Griffin wrote: > Hello Guixlings, > > One thing I think the Guix project should do is work with the > reproducible builds folks to publish a document explaining the issues > involved with self-hosted compilers. It should encourage language >

Publishing an Official Statement on Self-Hosted Compilers

2016-05-05 Thread Alex Griffin
Hello Guixlings, One thing I think the Guix project should do is work with the reproducible builds folks to publish a document explaining the issues involved with self-hosted compilers. It should encourage language communities to continuously maintain some way to build their language starting