From: Ophidiophobia <Ophidiophobia@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: LanguageTool: discontinue packaging like Arch
Date: Thu, 23 Feb 2023 16:02:08 +0100 [thread overview]
Message-ID: <20230223150208.KLQt0z8hCvGo_1UmsbC-hl5-TmNX3AtGFGcA6mNS9gE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42390@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
New comment by Ophidiophobia on void-packages repository
https://github.com/void-linux/void-packages/pull/42390#issuecomment-1441939518
Comment:
Honestly I am in favor of switching to actually building from source and also upgrade to 6.0. I think the template should never had pulled in the dist files but here we are.
The main reason I did not go that route are:
- not sure how long compiling would take
- unsure which version LanguageTool actually ships on their website
- not sure if I would introduce any weird behaviour by unwittingly crate something slightly different
- we can have a long debate if LanguageTool (or any java application) should use dependencies from common sources (we have java-commons-io) and run into java's version of dll hell and maybe reintroduce class path hell or keep it sane and simple and have each app keep dependencies in their own directory
So yeah. Compiling from source is better in my opinion but I wanted to fix packaging quickly so users can easily use LanguageTools from other apps again.
next prev parent reply other threads:[~2023-02-23 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 0:33 [PR PATCH] " Ophidiophobia
2023-02-22 0:42 ` [PR PATCH] [Updated] " Ophidiophobia
2023-02-23 10:47 ` Eloitor
2023-02-23 15:02 ` Ophidiophobia [this message]
2023-02-23 15:16 ` Ophidiophobia
2023-05-25 1:53 ` github-actions
2023-06-08 2:04 ` [PR PATCH] [Closed]: " github-actions
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=20230223150208.KLQt0z8hCvGo_1UmsbC-hl5-TmNX3AtGFGcA6mNS9gE@z \
--to=ophidiophobia@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).