all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Divya Ranjan <divya@subvertising.org>
To: Pjotr Prins <pjotr.public12@thebird.nl>,
	Olivier Dion <odion@efficios.com>
Cc: guix-devel@gnu.org, pjotr.public12@thebird.nl
Subject: Re: On a Guile-based Build-Tool complimenting Guix
Date: Sat, 28 Dec 2024 01:48:02 +0000	[thread overview]
Message-ID: <BCAE5518-EC50-4909-AAC9-8E7893595223@subvertising.org> (raw)
In-Reply-To: <20241221075300.g4s3ccluwmaumynk@mailx.thebird.nl>

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]

Hello Pjotr, glad to see that you'd be still interested in such a project.

> Where it comes to other targets, such as Debian distros and all, it is probably going to be too painful to handle to resolve all their demands.

Can you elaborate on what exactly would be hard to figure out for a Debian target?

And, I personally think just generating makefiles in Guile isn't really going to be better. I mean it'll save someone from writing a Makefile in, well, Make, but it will still have the issues of `make`. I believe it is an alternate build system that we should try.

Regards,
Divya Ranjan, Mathematics, Philosophy and Libre Software

[-- Attachment #2: Type: text/html, Size: 749 bytes --]

  reply	other threads:[~2024-12-28  1:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 20:12 On a Guile-based Build-Tool complimenting Guix Divya Ranjan
2024-12-19 21:08 ` Sergio Pastor Pérez
2024-12-28  1:55   ` Divya Ranjan
2024-12-19 21:17 ` Janneke Nieuwenhuizen
2024-12-20  0:06   ` indieterminacy
2024-12-28  1:53   ` Divya Ranjan
2024-12-19 21:33 ` Olivier Dion
2024-12-21  7:53   ` Pjotr Prins
2024-12-28  1:48     ` Divya Ranjan [this message]
2024-12-28  1:38   ` Divya Ranjan
2024-12-28 17:50   ` Ludovic Courtès
2024-12-20 17:31 ` Attila Lendvai
2024-12-28  1:43   ` Divya Ranjan
2024-12-27  0:41 ` Fi
2024-12-28  1:51   ` Divya Ranjan

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BCAE5518-EC50-4909-AAC9-8E7893595223@subvertising.org \
    --to=divya@subvertising.org \
    --cc=guix-devel@gnu.org \
    --cc=odion@efficios.com \
    --cc=pjotr.public12@thebird.nl \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.