unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jgart <jgart@dismail.de>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Guix Goals: One Hackable Developer Tool To Rule Them All
Date: Sun, 16 Oct 2022 12:54:42 -0500	[thread overview]
Message-ID: <20221016125442.GD2722@dismail.de> (raw)
In-Reply-To: <866dce757bafc9e92c64582b3bc3b50a792c4e7e.camel@gmail.com>

On Sun, 16 Oct 2022 15:11:38 +0200 Liliana Marie Prikler <liliana.prikler@gmail.com> wrote:
> Am Donnerstag, dem 13.10.2022 um 01:07 -0500 schrieb jgart:
>   #!/bin/sh
>   exec guix shell -m "$0" -- guile -e main -s "$0" "$@" 
>   !#
> 
>   (define (main args) ...)
> 
>   ...
> 
>   (specifications->manifest ...)
> 
> Of course, it'd be hell of a lot cleaner to separate manifest and
> business logic, but who am I to stop you?

Hi lilyp,

Yup, the latter is what I'm proposing instead of implementing a goal
for each lang à"ala carte" as a script for each project.

That would be like implementing part of a build-system everytime
when needed like we currently do when we needing to run pytest
instead their being first class support like was being worked on in:
https://github.com/guix-mirror/guix/tree/wip-python-pep517.

I'd like for "goals" to have first class support like guix home configs,
etc. do. But thanks for reminding us that we can just implement it
directly as needed in a script for each project. That's a testament to
the extensibility of Guix!

> Of course, it'd be hell of a lot cleaner to separate manifest and
business logic, but who am I to stop you?

I just need to find the time to implement the framework/system and
propose it again with a patch series ;() Not sure when that will be yet...

all best,

jgart


  reply	other threads:[~2022-10-16 17:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13  6:07 Guix Goals: One Hackable Developer Tool To Rule Them All jgart
2022-10-13 13:03 ` zimoun
2022-10-13 13:56 ` pinoaffe
2022-10-13 14:34   ` indieterminacy
2022-10-13 14:55     ` pinoaffe
2022-10-14  2:24       ` jgart
2022-10-16 13:11 ` Liliana Marie Prikler
2022-10-16 17:54   ` jgart [this message]
2022-10-16 18:41     ` jgart
2022-10-16 18:50     ` Liliana Marie Prikler
2022-10-16 20:03       ` jgart
2022-10-16 23:22         ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2022-10-17 19:08         ` Liliana Marie Prikler

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=20221016125442.GD2722@dismail.de \
    --to=jgart@dismail.de \
    --cc=guix-devel@gnu.org \
    --cc=liliana.prikler@gmail.com \
    /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).