unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: swedebugia <swedebugia@riseup.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Moving general useful procedures to the utils-modules
Date: Fri, 28 Dec 2018 16:10:09 +0100	[thread overview]
Message-ID: <877eft4rhq.fsf@elephly.net> (raw)
In-Reply-To: <d3796320-dfb6-4807-c1c5-656190d67f8e@riseup.net>


swedebugia <swedebugia@riseup.net> writes:

> I found this in guix/build/cargo-build-system.scm:
>
> (define (touch file-name)
>   (call-with-output-file file-name (const #t)))
>
> I think we should move useful ones like this to (build utils) and
> consider merging (build utils) and (import utils) into a single
> utils-module.

While I agree that we should avoid duplication, note that (guix build
utils) is build-side code, so changing it causes rebuilds.

> I think we should also consider factoring out some of these utils in a
> separate guix-utils library that can be used by other guile-projects
> WITHOUT depending on the whole of guix.

(guix import utils) may not necessarily be useful.  I’m wary of packages
that provide “miscellaneous” tools and I think we should avoid that.
In more focused cases like the monads code I agree that it would be nice
to break these out into separate projects.

--
Ricardo

      reply	other threads:[~2018-12-28 15:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-26 12:17 Moving general useful procedures to the utils-modules swedebugia
2018-12-28 15:10 ` Ricardo Wurmus [this message]

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=877eft4rhq.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=swedebugia@riseup.net \
    /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).