From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id eMuVHBYiSGOuSwEAbAwnHQ (envelope-from ) for ; Thu, 13 Oct 2022 16:35:02 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id wJ/EHBYiSGMVCAEA9RJhRA (envelope-from ) for ; Thu, 13 Oct 2022 16:35:02 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 4739C2FA39 for ; Thu, 13 Oct 2022 16:35:02 +0200 (CEST) Received: from localhost ([::1]:48980 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oizIb-0005i4-Eg for larch@yhetil.org; Thu, 13 Oct 2022 10:35:01 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:52508) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oizIE-0005Na-MI for guix-devel@gnu.org; Thu, 13 Oct 2022 10:34:38 -0400 Received: from libre.brussels ([144.76.234.112]:43896) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oizIB-00032y-Ok for guix-devel@gnu.org; Thu, 13 Oct 2022 10:34:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=libre.brussels; s=mail; t=1665671665; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rAZGybsn3932XTgNKBrF1kjMTYCnG1NVIAc7enpRPpg=; b=SIdDPf453VLxumsa8qJuPk1g1VsSPLo84qPAfyUPSIqdRjB8hjkZw3+tq5QQBK2sOLsEfe WVbG+HozzPNGU/tHXlr+ygFqwY1Nvdvlyo/j8+/AxCRgisUSCYvTjq0oewMppHg+oKLisp lne2S8I2stQNGdrDSs20Y3ErSnc1G74= MIME-Version: 1.0 Date: Thu, 13 Oct 2022 16:34:25 +0200 From: indieterminacy To: pinoaffe Cc: jgart , guix-devel@gnu.org Subject: Re: Guix Goals: One Hackable Developer Tool To Rule Them All In-Reply-To: <87a65zrepm.fsf@airmail.cc> References: <20221013010703.GB27375@dismail.de> <87a65zrepm.fsf@airmail.cc> Message-ID: X-Sender: indieterminacy@libre.brussels Organization: Icebreaker Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=144.76.234.112; envelope-from=indieterminacy@libre.brussels; helo=libre.brussels X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1665671702; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=rAZGybsn3932XTgNKBrF1kjMTYCnG1NVIAc7enpRPpg=; b=Uw6BBeUTTE98anf1lktjF1af6tlfiZtq20TkD6chcZgpCKpUk9fEqkLs6BdwrnyZ9k8L2K sHX4Mg+APhTvOG7peOzOKiPna/UVFsWhp3xP2QMHMPUJeuw/62wKyjx7BFpNTXNb5U9pp3 +46oWQBRQju5HZp0pJ4rFIa87NzSioFBZH/zBSqDl4cJpVDe3jioez45xIBynYoK8Y92bT S9+3EcnZjrV7+UR8B7a0cwcx0EVkcjwVKCTvW6R/bDli8DU2JX4A1Q5Ozkto4FXESUtD6R 2f4IFSmv6Lbrsuc2eptHIsssXfJhaew5RQgNOVhmA0IfqGxiuuUSx4ZbgY/s6w== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1665671702; a=rsa-sha256; cv=none; b=GQlUI94Ewg/tMy04Rxm40MjES7Tf9WHjuTfUK8gBW4mRbZ8loGHzmL3jA5rpKqdpyZRxcr 1MU42HzsLOhP3QaxjQDm5LHow5CdgRr3Ey0KKBtxykUPVmHQfYMAoJ75yfqVCXS7KCv/Hl PBF2lzoGq7N6BrLfXkd6LOLcIMKvKCdMGLSWy3sukdz2urAmbXS9QhyyIcrf639ozqSceS ZCykoGILIDl0+u0p6pUgb/RHVcNmLy5qDVPfuHwSOO254JhtKVQ+6ic4kh8Yyghrt4qBOD nrR1vhgSSp7CO5cinqZ0HV6f7iedhyOZTjE7r4w3XTT4mv5w2vPP8ABzT9SRjw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=libre.brussels header.s=mail header.b=SIdDPf45; dmarc=pass (policy=none) header.from=libre.brussels; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -2.40 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=libre.brussels header.s=mail header.b=SIdDPf45; dmarc=pass (policy=none) header.from=libre.brussels; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 4739C2FA39 X-Spam-Score: -2.40 X-Migadu-Scanner: scn1.migadu.com X-TUID: KJl1MYVrLml3 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 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