all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: gradle not supported?
Date: Wed, 24 Jul 2019 23:55:28 +0200	[thread overview]
Message-ID: <87lfwn9jxr.fsf@elephly.net> (raw)
In-Reply-To: <20190724152859.741c8ad4@gmail.com>


Hi Jesse,

> I noticed when I search the code for gradle I get
> - code deleting the provided gradle jar
> - comments about keeping a version of two different packages back
>   because they require gradle. 
>
> I'm guessing the gradle jar is deleted because it isn't compiled for
> guix. But why are these packages (java-htsjdk and java-picard in
> gnu/packages/bioinformatics.scm) held back to not depend on gradle?

That’s because we can’t build packages that depend on gradle without
depending on an opaque binary that we cannot (yet) build.

> If I need a package that uses gradlew to build, what is the best
> solution for defining it?

IIUC gradle usually downloads a version of gradle as the first step.
Building a package that uses gradlew may currently require a lot of
manual work to essentially avoid the use of gradle as we have no gradle
build system yet.

A more constructive way would be to figure out a way to provide a
gradle-build-system that works around the problems we have with gradle
in one way or another, so that this is fixed for all future packages
depending on gradle.

Tricky.

-- 
Ricardo

  reply	other threads:[~2019-07-24 21:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 21:28 gradle not supported? Jesse Gibbons
2019-07-24 21:55 ` Ricardo Wurmus [this message]
2019-07-25  7:50 ` Hartmut Goebel
2020-03-13  9:30   ` Pierre Neidhardt
2020-03-13 11:49     ` Julien Lepiller
2020-03-13 13:19       ` Pierre Neidhardt

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lfwn9jxr.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=jgibbons2357@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.