From: Skyler Ferris via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Divya Ranjan <divya@subvertising.org>
Cc: guix-devel@gnu.org, pjotr.public12@thebird.nl
Subject: Re: On a Guile-based Build-Tool complimenting Guix
Date: Sat, 04 Jan 2025 10:06:13 +0000 [thread overview]
Message-ID: <OBKV9i5-smnOjTjTsk5XAxKLWI51KjhOqVrzvb8H2dulyGJ3pnspFpydZCTbCYjs0n-jug7l3v5fP8q4XJHkcSmQhyLIcLtKleX6aV0WYq8=@skyler-ferris.me> (raw)
In-Reply-To: <87wmfvo2je.fsf@subvertising.org>
Hi all! I just want to mention some theoretical benefits that could arise from using a Guix-aware build-system.
A Guix-aware build system could improve upon the traditional timestamp-based rebuilding heuristic by using a content address heursitic. This benefits developers using the Guix-aware build system because it reduces the number of rebuilds that occur and enables transparent artifact sharing when multiple versions of a project are checked out to different locations. It benefits Guix itself because it enables incremental builds inside of Guix (including on the build server).
A Guix-aware build system could remove overhead for package maintainers. If the source repository contains the build code - which in proper Guix style is deterministic and contain precise dependency information - the packager only has to verify the source hash. This benefits packagers because they can focus on the social value provided by packaging (discoverability, pre-configuration) without worrying technical problems such as a library updated for an otherwise unrelated package.
Regards,
Skyler
next prev parent reply other threads:[~2025-01-04 16:20 UTC|newest]
Thread overview: 20+ 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
2025-01-10 17:31 ` Sergio Pastor Pérez
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-31 6:01 ` Pjotr Prins
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
2024-12-31 1:58 ` Fi
2025-01-04 10:06 ` Skyler Ferris via Development of GNU Guix and the GNU System distribution. [this message]
2025-01-06 19:59 ` Hartmut Goebel
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='OBKV9i5-smnOjTjTsk5XAxKLWI51KjhOqVrzvb8H2dulyGJ3pnspFpydZCTbCYjs0n-jug7l3v5fP8q4XJHkcSmQhyLIcLtKleX6aV0WYq8=@skyler-ferris.me' \
--to=guix-devel@gnu.org \
--cc=dev@skyler-ferris.me \
--cc=divya@subvertising.org \
--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 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).