From: loreb <loreb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sbt has no source code
Date: Mon, 20 Dec 2021 21:45:30 +0100 [thread overview]
Message-ID: <20211220204530.atfP_DSgw9cxlqlQ_PJ-y8nFfE7sa_NBROI9iIL9NNY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34597@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
New comment by loreb on void-packages repository
https://github.com/void-linux/void-packages/issues/34597#issuecomment-998256921
Comment:
You're right; and I tried installing it in a vm, running "sbt" even in an empty directory will download all sorts of dependencies from the internet...
A couple of possible solutions (in alphabetical order):
1. build.sh - run the tool, say in a vm, write down the steps required to compile and hack together a stupid shell script that does exactly that
2. debian - they package it successfully at https://packages.debian.org/sid/sbt
3. go - when the go package rewrote its compiler in go (used to be in C), void added the go1.12-bootstrap package, something like that could be done (and it looks to me that it's basically what they are doing in debian, plus patches to avoid the "download from the internet" step)
4. history - check the project's history, they must have started with maven or gradle or whatever, so one should be able to build some ancient version and use that... you get the idea.
My impression from toying with it for 5 minutes is that I'm glad that I'm not a scala programmer and I can leave the problem to somebody else.
PS
Good job noticing!
next prev parent reply other threads:[~2021-12-20 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 0:47 [ISSUE] " HiPhish
2021-12-20 20:45 ` loreb [this message]
2021-12-30 22:18 ` [ISSUE] [CLOSED] " q66
2021-12-30 22:18 ` q66
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=20211220204530.atfP_DSgw9cxlqlQ_PJ-y8nFfE7sa_NBROI9iIL9NNY@z \
--to=loreb@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).