From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Nieuwenhuizen Subject: Re: Preparing the reduced bootstrap tarballs Date: Wed, 21 Nov 2018 21:32:16 +0100 Message-ID: <87muq22mun.fsf@gnu.org> References: <87a7m61r4m.fsf@ITSx01.pdp10.guru> <8736ryutoy.fsf@netris.org> <87ftvys00m.fsf@gnu.org> <87r2ff4utb.fsf@ngyro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53447) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gPZE4-0003AC-Ht for guix-devel@gnu.org; Wed, 21 Nov 2018 15:35:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gPZAg-0000RT-FM for guix-devel@gnu.org; Wed, 21 Nov 2018 15:32:27 -0500 In-Reply-To: <87r2ff4utb.fsf@ngyro.com> (Timothy Sample's message of "Tue, 20 Nov 2018 10:45:04 -0500") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Timothy Sample Cc: guix-devel@gnu.org, Rutger van Beusekom Timothy Sample writes: Hello Timothy! >> The plan is to have Guile and Gash initially replace all coreutils&co >> and build them from source early in the bootstrap phase, right after >> having built tcc and GNU make. We have managed to build GNU make >> without any dependency on any of the tool you mention (except for >> Guile). >> >> We're not there yet, gash cannot build mes or tcc. Also, the latest mes >> 0.18 release cannot support buillding bash yet. Lots of fun hacking >> todo! > > I wanted to let you know that I=E2=80=99ve been doing more work on the li= ttle > Shell backend that we were talking about earlier. It=E2=80=99s kind of l= ike the > worse-is-better version of Gash: it is certainly not as nice, but the > development pace is much faster. I did take a look at just working on > Gash directly, but it looked like it was going to be a lot slower. Oh, that's great news! We have been making good progress on Gash. The parser has been completely revamped. The next target is to add a transformation that should result in a eval'able shelly Guile script, ideally something that you'd want to write by hand. To achieve that will take some time. It would be nice if we could work together shaping this shelly script language . If Gash and Geesh would produce (after transformation) the same shelly script language, we can also share the backend implementation, WDYT? > So, keeping in mind that software estimates are very unreliable, I would > say that I might have a workable interpreter in the next week or two. > There are three big features missing: globbing, asynchronous commands, > and arithmetic substitutions. I am almost finished globbing, > asynchronous commands should be pretty easy, and I plan to leave > arithmetic substitutions on the road-map for as long as possible (it=E2= =80=99s a > little bit boring). Hehe. I had a look and you did make lots of progress! > After I get those first two features working, I am going to start > testing running build scripts for Bash. I will contact you then in case > you have any new advice on which scripts are important or anything else. Great, Keep up the good work! --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.com