From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Sassmannshausen Subject: Re: Call for project proposals: Guix and Outreachy Date: Sat, 27 Jan 2018 12:45:52 +0100 Message-ID: <87h8r7msnj.fsf@gmail.com> References: <87fu6y27re.fsf@elephly.net> <874ln896pq.fsf@gmail.com> <20180127020156.pw4pjxijbxlkyaew@floriannotebook> Reply-To: alex.sassmannshausen@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60575) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1efOvo-0004It-Mw for guix-devel@gnu.org; Sat, 27 Jan 2018 06:46:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1efOvl-00039S-Ia for guix-devel@gnu.org; Sat, 27 Jan 2018 06:46:00 -0500 Received: from mail-wm0-x233.google.com ([2a00:1450:400c:c09::233]:51495) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1efOvl-000390-Ad for guix-devel@gnu.org; Sat, 27 Jan 2018 06:45:57 -0500 Received: by mail-wm0-x233.google.com with SMTP id r71so5852214wmd.1 for ; Sat, 27 Jan 2018 03:45:57 -0800 (PST) In-reply-to: <20180127020156.pw4pjxijbxlkyaew@floriannotebook> 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: "pelzflorian (Florian Pelz)" Cc: guix-devel@gnu.org Hi pelzflorian (Florian Pelz) writes: > Hello, > > On Fri, Jan 26, 2018 at 12:53:37PM +0100, Alex Sassmannshausen wrote: >> A second step might be a simplified Guile build system, which does not >> rely on autotools infrastructure. I believe this was discussed in the >> past: it would be a "beginners build system" for *Guile only* packages >> for quick and easy sharing in the Guix community. > > By beginners build system, do you mean a Guix build system that just > copies the modules directory and compiles? Yes — it would just carry out the steps so that if the Guile package is a propagated input to anything else, or if it is installed directly, the Guile package would be available to the Guile executable in that context. So the files would simply be installed in the ACTUAL_GUILE_VERSION site dir & ccache dir. > Forgive my ignorance as someone who has no deep understanding of > Guile/Guix, but I think it would be better if even simple Guile only > packages used a build system like Meson or Autotools. Even Guile only > packages should not need Guix or manual copying. The syntax of > Autotools is too complicated IMHO, but using a general purpose build > system like Meson for simple C projects is no more work than listing > the source files and data files like pkg-config and this should apply > to Guile projects as well. I sympathise with your perspective, but this proposed second step would be quite "selfish" from the perspective of Guix and Guile: it would be a strong improvement in comparison to what we have now (no widely used package manager, or project bootstrapping system for Guile), whilst not committing to infrastructure behind it. As such it doesn't aim to "care" about non-guix use-cases. To phrase it strongly I think Guix is the de-facto Guile package manager, so a good first step is a simple build environment for that specific package manager. We could then gradually build on the tooling to allow a migration path to autotools. > That said, a beginners Guix build system for pure Guile projects is > done much more easily than making simple general purpose build systems > support Guile. I’d like to take a look at Meson support for Guile and > Guile implementations of Ninja and Meson, but I probably can’t/won’t > commit the time… Well maybe… I would be very interested to hear about your further research into this area for sure! The above stuff is just my opinion so far :-) Cheers, Alex