unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Adriano Peluso <randomlooser@riseup.net>
To: Pjotr Prins <pjotr.public12@thebird.nl>,
	Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Idea: a meta language for (language) build systems - npm, Racket, Rust cargo
Date: Tue, 01 Jun 2021 07:50:01 +0200	[thread overview]
Message-ID: <0744d2430aa74225a6a7396a06e0d2a7bc4ccbc6.camel@riseup.net> (raw)
In-Reply-To: <20210531174748.mhaelcqwmo7degfc@thebird.nl>

Il giorno lun, 31/05/2021 alle 19.47 +0200, Pjotr Prins ha scritto:
> On Sun, May 30, 2021 at 09:17:20PM +0200, Konrad Hinsen wrote:
> > How about pushing all the other package manager towards producing
> > sexp-packs, and helping them to get there?
> 
> I have a feeling they won't be that interested ;).
> 
> My thoughts are that every software package simply consists of files
> that need to be compiled (if not interpreted) and be copied in place.
> 
> As Guix takes care of the first and the last - the issue centers
> around building. The idea is to dress down these language specific
> builders, such as cargo, so you don't have all the included
> complexity. 
> 
> A sexp-pack would represent the most simple build instructions to
> build a package on its own. Now, of course the current guix-builders
> solve that too. But, what I am proposing is to split out the actual
> build step into a package definition, so as to present something
> simpler to Guix.
> 
> I found a cargo -> ninja converter. It is that kind of idea. Guix
> would use ninja with rustc instead of cargo. A stripped down cargo
> could potentially work too - but cargo is a complex beast.
> 
> A simplified build step would make it easier to troubleshoot these
> packages.
> 
> See what I mean?

You mean to break the chain introducing an intermediate step

With intermediate step, I mean a new kind of entity with its own format

I like the idea

Many times, breaking long chains makes them more understandable to me

It's the old idea of composability, if you want

It's like refactoring a huge procedure in several smaller ones

It also resembles a sort of ETL process or some sort of "data science"
task of "massaging" data for some later analisys phase

In a way, doing this would in itself push language communities to think
about their approach (of releasing blobs)

I doubt they would start such an initiative themselves, they wouldn't
have begun releasing blobs in the first place



  reply	other threads:[~2021-06-01 13:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-30  8:38 Idea: a meta language for (language) build systems - npm, Racket, Rust cargo Pjotr Prins
2021-05-30 19:17 ` Konrad Hinsen
2021-05-31 17:47   ` Pjotr Prins
2021-06-01  5:50     ` Adriano Peluso [this message]
2021-06-01  6:24     ` Leo Prikler
2021-06-01  7:23       ` Pjotr Prins
2021-06-01  8:12         ` Leo Prikler
2021-06-01  8:59       ` Adriano Peluso
2021-06-01  9:11         ` Leo Prikler
2021-06-01 10:52           ` Adriano Peluso
2021-06-01 11:03             ` Leo Prikler
2021-06-01 11:28               ` Adriano Peluso
2021-06-01 15:22                 ` Leo Prikler
2021-06-01  7:56     ` Konrad Hinsen
2021-06-01 23:35       ` Joshua Branson
2021-06-08 13:11     ` Ludovic Courtès
2021-06-14 14:29       ` Pjotr Prins
2021-06-14 22:04         ` Leo Prikler
2021-06-15  8:48           ` Pjotr Prins
2021-06-15 10:08           ` Ricardo Wurmus
2021-06-20 15:46         ` Ludovic Courtès

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=0744d2430aa74225a6a7396a06e0d2a7bc4ccbc6.camel@riseup.net \
    --to=randomlooser@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=konrad.hinsen@fastmail.net \
    --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).