unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: Charlie Ritter <chewzerita@posteo.net>, Nils Gillmann <ng0@n0.is>,
	31250@debbugs.gnu.org
Subject: [bug#31250] [PATCH] Add leiningen
Date: Sat, 28 Apr 2018 22:44:19 +0200	[thread overview]
Message-ID: <87bme3awnw.fsf@gnu.org> (raw)
In-Reply-To: <20180427051633.fmszqyynlhvtjqt7@thebird.nl> (Pjotr Prins's message of "Fri, 27 Apr 2018 07:16:33 +0200")

Pjotr Prins <pjotr.public12@thebird.nl> skribis:

> On Thu, Apr 26, 2018 at 12:41:32PM +0000, Nils Gillmann wrote:
>> > The policy for Guix is to build things from source.  So we would have to
>> > provide Leiningen and its dependencies as packages built from source,
>> > and to remove the auto-download functionality from the script.
>> 
>> But this is on first run, not during the installation as far as I remember.
>> So in my opinion that's not an immediate blocker for the initial package.
>> The obvious fix afterwards is to apply the building from source.
>
> We also packaged tools like conda that download binaries when run.

True, that’s not great, and Leiningen may actually do the same thing as
part of its normal job…

I think it’s good to estimate how difficult it would be to build
Leiningen from source, and then we can decide what to do.

Ludo’.

  reply	other threads:[~2018-04-28 20:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 15:44 [bug#31250] [PATCH] Add leiningen Charlie Ritter
2018-04-25 20:54 ` Ludovic Courtès
2018-04-26 12:41   ` Nils Gillmann
2018-04-27  5:16     ` Pjotr Prins
2018-04-28 20:44       ` Ludovic Courtès [this message]
2023-07-26 13:21 ` guix-patches--- via

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=87bme3awnw.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=31250@debbugs.gnu.org \
    --cc=chewzerita@posteo.net \
    --cc=ng0@n0.is \
    --cc=pjotr.public12@thebird.nl \
    /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).