Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Weird organization of maven packages
Date: Fri, 16 Oct 2020 20:07:16 +0200	[thread overview]
Message-ID: <20201016180716.oOdNos8ZVWH0K2xdXBl8p-J59w2fXJ_LCGLDBpD2UWE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24617@inbox.vuxu.org>

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

Closed issue by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/24617

Description:
The `apache-maven-bin` package is prebuilt, has files in `/opt`, but symlinks to its files in `/usr/bin`.

On the other hand, the `apache-maven` package has compiled java stuff in `/usr/share`, requires sourcing a profile file to get access to its tools, and if `apache-maven-bin` is installed at the same time, its tools will be first in the PATH anyway, so the profile doesn't really help.

Then, some packages have `apache-maven`, others `apache-maven-bin` in `hostmakedepends`.

IMO neither of these packages really fit the proper packaging guidelines. So my questions are:

- should  the maven binaries become alternatives, or should `apache-maven` become the preferred provider of maven stuff?
- should we move all templates to `apache-maven` (and potentially remove `apache-maven-bin`? Why is it in the repos?)

      parent reply	other threads:[~2020-10-16 18:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 19:46 [ISSUE] Weird organization in " ericonr
2020-09-02 20:02 ` Weird organization of " the-maldridge
2020-09-02 20:03 ` ericonr
2020-09-17  9:03 ` fosslinux
2020-09-17 13:27 ` ericonr
2020-10-16 18:07 ` ericonr [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

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

  git send-email \
    --in-reply-to=20201016180716.oOdNos8ZVWH0K2xdXBl8p-J59w2fXJ_LCGLDBpD2UWE@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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.
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 NNTP newsgroup(s).