unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Declan Tsien <declantsien@riseup.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>, guix-devel@gnu.org
Subject: Re: Build LanguageTool use maven-build-system?
Date: Wed, 26 Oct 2022 13:20:31 +0800	[thread overview]
Message-ID: <87k04ngnz4.fsf@riseup.net> (raw)
In-Reply-To: <33d397f581b910871b69078b4499087751042a66.camel@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]


Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

> What Julien means is that if you were trying to write an importer,
> you'd end up writing one that produces something like this
>
>   (define-public java-language-tool
>      (package 
>        (name "java-language-tool")
>        (version "6.0")
>        (source this-thing-raises-an-error)
>        ...
>        (inputs (list java-commons-cli ...))
>        (native-inputs (list java-junit ...))
>        ...))
>
>   (define-public java-commons-cli
>      (package
>         (name "java-commons-cli")
>         (version some-version)
>         (source this-thing-raises-an-error)
>         ...))
>
> In other words, you won't be able to actually build language-tool until
> you insert proper sources in all the source fields – which Julien fears
> maven, being a binary distribution system first and foremost, won't
> deliver on its own.
>
> Cheers

I see. Thanks.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 690 bytes --]

      reply	other threads:[~2022-10-26  5:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25  2:10 Build LanguageTool use maven-build-system? Declan Tsien
2022-10-25 11:30 ` Julien Lepiller
2022-10-25 23:56   ` Declan Tsien
2022-10-26  5:06     ` Liliana Marie Prikler
2022-10-26  5:20       ` Declan Tsien [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=87k04ngnz4.fsf@riseup.net \
    --to=declantsien@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=liliana.prikler@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 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).