Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] Weird organization in maven packages
@ 2020-09-02 19:46 ericonr
  2020-09-02 20:02 ` Weird organization of " the-maldridge
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: ericonr @ 2020-09-02 19:46 UTC (permalink / raw)
  To: ml

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

New 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.

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?)

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2020-10-16 18:07 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-02 19:46 [ISSUE] Weird organization in maven packages 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 ` [ISSUE] [CLOSED] " ericonr

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).