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

Sorry if this comes off as facetious (because this is an interesting 
proposal) but hasnt Make cornered a lot of these usecases well enough?

On 13-10-2022 15:56, pinoaffe wrote:
> Hi,
> 
> I think that (if done well) this would greatly simplify my workflow in
> many software projects, so I think it's a good idea.
> 
> In the rest of my email, I more or less assume that there is a
> one-to-one correspondence between software projects and guix packages,
> even though this is clearly not the case.  I nonetheless make this
> assumption since it is the case (or can be made the case) for many of
> the software projects on which one might want to work using guix.
> 
> jgart <jgart@dismail.de> writes:
>> The various language ecosystems have their own linters, formatters,
>> typecheckers, repls, test runners, etc.
>> 
>> What if Guix could manage them all?
>> 
>> `guix lint` in a python project would run mypy.
>> `guix lint` in a haskell project would run hlint.
>> `guix lint` in an erlang project would run dialyzer.
> 
> These would require some sort of configurability, since most
> languages/projects have not just one linter.  Even if there's a
> "monopoly" there might be different settings/versions of said linter.
> 
> Do you propose that such configuration is added to packages?  Or should
> this go somewhere else?
> 
> Furthermore, in many projects there are various different languages at
> once (e.g., a python webapp with client-side javascript and css), so it
> would probably be useful to mirror the build-phases approach in guix
> packaging.  It might even be possible to set up (somewhat) sane 
> defaults
> based on the build-system used by the local project.
> 
>> `guix fmt` in a python project would run black.
>> `guix fmt` in a haskell project would run ormolu.
>> `guix fmt` in a erlang project would run erlfmt.
> 
> My comments regarding linters apply here as well
> 
>> `guix repl` in a python project would run ptpython or some other 
>> configured repl.
>> `guix repl` in a haskell project would run ghci.
>> `guix repl` in a erlang project would run erl.
> 
> This should be fairly easy to implement, assuming that there is just 
> one
> repl associated to each project one might want to use this command 
> with.
> It should (imo) be possible to configure/pass arguments to the repl on 
> a
> per-project basis and whenever you run `guix repl`
> 
>> `guix test` in a python project would run pytest or unittest.
>> `guix test` in a haskell project would run hunit.
>> `guix test` in a erlang project would run eunit.
> 
> Should I read this as a proposal to add an extra command to build (and
> test) the local project's guix package, or do you propose to make this
> do something different?  Because I'm not sure the latter would be a 
> good
> idea, if there is a need to do testing in some other way than currently
> possible I'd think it would be more valuable (and more clean) to extend
> the current testing facilities to incorporate this.
> 
>> `guix run` in a python project could start a flask app listening on a 
>> particular port.
>> `guix run` in a ruby project could start a puma server.
>> `guix run` in a haskell project could run a pre-configured script or 
>> Main.hs
>> `guix run` in a erlang project could start a cowboy server.
> 
> I'm not sure how widely this may be applicable, since many projects or
> packages don't have just one way to run them, they may even contain
> several different executables or modules.
> 
>> The idea would be to have Guix provide a configurable CLI wrapper
>> subcommand around all language ecosystem developer tools. In other 
>> words
>> it's the same Guixy thesis applied to developer tooling. I think this
>> could take the Guix developer experience to the next level.
> 
> Kind regards,
> pinoaffe

-- 
Jonathan McHugh
indieterminacy@libre.brussels


  reply	other threads:[~2022-10-13 14:35 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 [this message]
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
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=b8465f9e1774827d018140b7b647aa97@libre.brussels \
    --to=indieterminacy@libre.brussels \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --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).