unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jgart <jgart@dismail.de>
To: pinoaffe <pinoaffe@airmail.cc>
Cc: indieterminacy <indieterminacy@libre.brussels>,
	pinoaffe <pinoaffe@airmail.cc>,
	guix-devel@gnu.org
Subject: Re: Guix Goals: One Hackable Developer Tool To Rule Them All
Date: Thu, 13 Oct 2022 21:24:21 -0500	[thread overview]
Message-ID: <20221013212421.GB25754@dismail.de> (raw)
In-Reply-To: <87zgdzpxzb.fsf@airmail.cc>

On Thu, 13 Oct 2022 16:55:33 +0200 pinoaffe <pinoaffe@airmail.cc> wrote:

What I proposed is not an original idea but what the pants project
does. See this doc:

https://www.pantsbuild.org/v1.29/docs/goals

Pants fully supports Python but they are quickly working on golang,
java, and other languages.

zimoun, I'm mostly just brainstorming the general idea at the moment. I don't
mind if it takes the form of `guix project ...` or some other form.

pinoaffe, I agree that the developer commands should be completely
Guile configurable and hackable to our hacker heart's content, of
course. That's why we're all here ;()

Jonathan,

> but hasnt Make cornered a lot of these usecases well enough?

That didn't stop Guixers from making the gnu-build-system that paren
hugs Make. Why stop there? If you want to call mypy from Make that's
fine but I'd like to call mypy from Make from guix or why not cut out
the middleman altogether? In the end I just want to see the same unifying
guix ui experience transfered to dev tools across the polyglot stack.

This infrastructure should be flexible enough to allow us to
easily go unix plumbing if need be.

Let's wrap the world in parens!

paren hugs,

jgart 





  reply	other threads:[~2022-10-14  2:26 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 [this message]
2022-10-16 13:11 ` Liliana Marie Prikler
2022-10-16 17:54   ` jgart
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=20221013212421.GB25754@dismail.de \
    --to=jgart@dismail.de \
    --cc=guix-devel@gnu.org \
    --cc=indieterminacy@libre.brussels \
    --cc=pinoaffe@airmail.cc \
    /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).