From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH]: Add Ant.
Date: Thu, 05 Feb 2015 13:34:07 +0100 [thread overview]
Message-ID: <87r3u44jwg.fsf@gnu.org> (raw)
In-Reply-To: <idjk304dysd.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Fri, 30 Jan 2015 17:21:54 +0100")
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
> A couple more things:
>
> * the installation script copies MS DOS batch scripts to $out/bin, which
> we could do without.
Indeed. :-) Would be best to get rid of them.
> * there are many launcher scripts for Ant: bash scripts, perl scripts,
> Python scripts ... Does ant-minimal need to get perl and python as
> inputs or can we do without these additional dependencies?
By launcher scripts, do you mean the ‘ant’ command? I suppose it’s
enough to have one of them, and the Bash version is probably the one
with the smallest disk space footprint, no?
> * to use Ant without problems ANT_HOME and JAVA_HOME really should be
> set appropriately (ANT_HOME to $out of the ant-minimal package,
> JAVA_HOME to $out of icedtea6). Should I suggest these two paths as
> search paths by adding something like this to ant-minimal (for
> ANT_HOME) and icedtea6 (for JAVA_HOME)?
>
> (native-search-paths
> (list (search-path-specification
> (variable "ANT_HOME")
> (files '(".")))))
Since Ant is generally used via the ‘ant’ command (AIUI), what about
wrapping that command so that ANT_HOME and JAVA_HOME are set
appropriately?
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-02-05 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 16:04 [PATCH]: Add Ant Ricardo Wurmus
2015-01-30 16:21 ` Ricardo Wurmus
2015-02-05 12:34 ` Ludovic Courtès [this message]
2015-02-06 15:51 ` Ricardo Wurmus
2015-02-07 22:55 ` Ludovic Courtès
2015-02-09 14:51 ` Ricardo Wurmus
2015-02-15 15:40 ` Andreas Enge
2015-02-15 16:13 ` Ricardo Wurmus
2015-02-15 16:21 ` Andreas Enge
2015-02-16 16:38 ` Ricardo Wurmus
2015-02-16 17:08 ` Andreas Enge
2015-02-05 12:32 ` Ludovic Courtès
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=87r3u44jwg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.