unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leandro Doctors <ldoctors@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Adding the maven-build-system
Date: Sun, 5 Apr 2020 16:48:15 -0300	[thread overview]
Message-ID: <CAAn03x6-_x_DACQV3rW4Z=6fZK1vAHNAa5yn_Vt5oszgmhxV6w@mail.gmail.com> (raw)
In-Reply-To: <87wo6uqof3.fsf@ambrevar.xyz>

On Sun, 5 Apr 2020 at 06:20, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> Hi Julien,
> thanks for this great summary, looking forward to it!

Same here, Julien :-)


> By the way, Leandro was planning to work on Clojars, so having a
> functioning maven build system might be helpful to that task.

Thanks for CCing me, Pierre :-)

Yes, assuming I get accepted for GSoC to work to add Clojars support
to Guix, Julien's work will be indeed helpful, as it would help me
evaluating whether The Central Repository (TCR, the new name of Maven
Central) is "Guixable enough" or not.
(That being said, the relative importance of TCR support for my
project would depend on the way I end up achieving Clojure CLI +
deps.edn support...)

As I mention in my proposal, an important aspect of TCR relates with
which types of package metadata it supports (or not). AFAIK, TCR does
not support explicit licensing and source repository metadata, very
important for Guix's values of freedom and reproducibility...

If full TCR support were to be somehow officially added to Guix, my
hypothesis (yet to be proven or refuted :) is that it should involve
mechanisms to deal with those limitations... Of course, all this does
not mean TCR support could not be eventually implemented as a
non-official Guix channel...
http://guix.gnu.org/manual/en/html_node/Channels.html#Channels

Best,
Leandro

      reply	other threads:[~2020-04-05 19:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04 15:52 Adding the maven-build-system Julien Lepiller
2020-04-04 20:51 ` Jack Hill
2020-04-04 23:01 ` Leo Famulari
2020-04-05  9:20 ` Pierre Neidhardt
2020-04-05 19:48   ` Leandro Doctors [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='CAAn03x6-_x_DACQV3rW4Z=6fZK1vAHNAa5yn_Vt5oszgmhxV6w@mail.gmail.com' \
    --to=ldoctors@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).