all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Divya Ranjan <divya@subvertising.org>
To: "Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>,
	guix-devel@gnu.org
Cc: pjotr.public12@thebird.nl, ngraves@ngraves.fr
Subject: Re: On a Guile-based Build-Tool complimenting Guix
Date: Sat, 28 Dec 2024 01:55:44 +0000	[thread overview]
Message-ID: <54333677-23B1-4191-AA76-24C2E181D484@subvertising.org> (raw)
In-Reply-To: <PAXP251MB03485125BA1FC31BF4D12349F3062@PAXP251MB0348.EURP251.PROD.OUTLOOK.COM>

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

Hello Sergio,

> While I don’t have a specific starting point in mind, I believe that an essential feature such a tool, is the ability of continuing builds from successful phases.

While I haven't looked Nicholas' patches carefully, how do you think we could use Guix's build-system functionality as it stands now for a proper build system?

Olivier, have you thought about this? A sort of custom build-system (loke gnu-build-system) for each package to build?

Regards,
Divya Ranjan, Mathematics, Philosophy and Libre Software

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

  reply	other threads:[~2024-12-28  1:56 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 [this message]
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
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=54333677-23B1-4191-AA76-24C2E181D484@subvertising.org \
    --to=divya@subvertising.org \
    --cc=guix-devel@gnu.org \
    --cc=ngraves@ngraves.fr \
    --cc=pjotr.public12@thebird.nl \
    --cc=sergio.pastorperez@outlook.es \
    /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.