From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Autotools formely: a blog post
Date: Sat, 7 Apr 2018 00:07:28 +0200 [thread overview]
Message-ID: <20180406220728.GA8995@thebird.nl> (raw)
In-Reply-To: <CAJ98PDwzK4VT5r+8Yk8s=1fwHjV+xf0MzsVzw36RL8N7Dd5HkQ@mail.gmail.com>
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
an environment. At the same time, with Guix you get a predictable
environment, so a make file (or similar) suffices. It is what I do in
all my development projects - I don't use autotools to develop and
deploy them. It greatly simplifies my existence :). Indeed, I have
never liked autotools (essentially a nasty hack) and only used them
before Nix/Guix. So, my approach is the same as yours :)
You can do without autotools once inside Guix and once you decide to
ignore targeting other distributions. Which I do, though I have ways
of deploying Guix built packages on other systems without Guix which
people also use. E.g.
https://github.com/genetics-statistics/GEMMA/releases
The top files include a binary Guix package installer. You can try it.
It is a way of distributing pre-built code on other systems. If you
are interested you could package your stuff too. Though it probably
makes less sense for a library for Guile until it becomes something
accepted by the Guile ecosystem.
Pj.
next prev parent reply other threads:[~2018-04-06 22:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 8:58 a blog post Catonano
2018-04-06 22:07 ` Pjotr Prins [this message]
2018-04-09 15:30 ` Guix-based build tool Ludovic Courtès
2018-04-09 15:53 ` julien lepiller
2018-04-11 8:02 ` Catonano
2018-04-16 16:59 ` Christopher Lemmer Webber
2018-04-18 3:50 ` Chris Marusich
2018-04-18 21:06 ` Ludovic Courtès
2018-04-18 21:09 ` Ludovic Courtès
2018-04-19 16:49 ` Catonano
2018-04-20 6:52 ` Catonano
2018-04-20 6:58 ` Catonano
2018-04-23 15:53 ` Ludovic Courtès
2018-04-20 20:13 ` Ricardo Wurmus
2018-04-07 3:35 ` a blog post Erik Edrosa
2018-04-07 9:53 ` Hartmut Goebel
2018-04-07 10:46 ` Tobias Geerinckx-Rice
2018-04-07 10:59 ` Catonano
2018-04-09 0:18 ` Chris Marusich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180406220728.GA8995@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=catonano@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).