Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.java > #11986
| From | Stephen Paul Weber <singpolyma@singpolyma.net> |
|---|---|
| Newsgroups | linux.debian.maint.java |
| Subject | Packaging a ./gradlew upstream? |
| Date | 2020-12-09 17:00 +0100 |
| Message-ID | <Bka2K-4wG-7@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
I am interested in packaging https://github.com/Anuken/Mindustry -- it uses the now somewhat-standard ./gradlew wrapper script style build system. This system downloads all kinds of dependencies (including the gradle build system itself) in binary form as part of running the build. I'm wondering if others have experience packaging upstreams using this kind of system and what the usual strategy is for building it with locally-installed dependencies from Debian instead of the network access it wants to do? Thanks for any tips,
Back to linux.debian.maint.java | Previous | Next — Next in thread | Find similar
Packaging a ./gradlew upstream? Stephen Paul Weber <singpolyma@singpolyma.net> - 2020-12-09 17:00 +0100
Re: Packaging a ./gradlew upstream? Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2020-12-09 20:40 +0100
Re: Packaging a ./gradlew upstream? Stephen Paul Weber <singpolyma@singpolyma.net> - 2020-12-09 20:50 +0100
Re: Packaging a ./gradlew upstream? Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2020-12-09 21:30 +0100
Re: Mindustry packaging Phil Morrell <debian@emorrp1.name> - 2020-12-10 01:40 +0100
csiph-web