Package Details: blockbench-bin 4.9.4-1

Git Clone URL: (read-only, click to copy)
Package Base: blockbench-bin
Description: A low-poly 3D model editor
Upstream URL:
Licenses: GPL3
Conflicts: blockbench
Provides: blockbench
Submitter: mrapplexz
Maintainer: Atakku (txtsd)
Last Packager: txtsd
Votes: 12
Popularity: 0.51
First Submitted: 2021-11-04 11:44 (UTC)
Last Updated: 2024-02-17 03:16 (UTC)

Latest Comments

1 2 Next › Last »

MithicSpirit commented on 2024-03-12 00:41 (UTC)

@furrykef also not a lawyer, but, from my understanding, the restrictions provided by the MIT license are a strict subset of those provided by the GPL3. That is, if you have access to code that is MIT-licensed, you are free to relicense it under the GPL3. Of course, this is not legal advice, and I'd recommend you contact a lawyer.

Either way, I think that the correct place to discuss this would be on their issue tracker, rather than on the AUR.

furrykef commented on 2024-03-11 22:28 (UTC)

I'm not a lawyer, but here's my understanding…

Since the MIT license is GPL compatible, switching a project's license from MIT to GPL is perfectly legitimate so long as the MIT license is properly followed for the contributions of developers who have not yet consented to the switch. That means a copy of the MIT license should be included and it should be made clear in some way which portions are MIT licensed and which are GPLed.

Unfortunately, Blockbench's devs aren't doing that, so (unless they did get everyone's consent) they are technically breaking the terms of the MIT license. However, in practice, few developers are likely to care, especially as long as older versions of the code are still available under the MIT license.

I think more important than the letter of the law here is the intent: someone who contributes to an MIT-licensed project clearly intends for their code to be usable in a GPLed project, since the MIT license and the GPL are compatible. That said, it'd still be nice if Blockbench properly followed the MIT license's terms.

MithicSpirit commented on 2024-03-11 06:25 (UTC) (edited on 2024-03-11 06:25 (UTC) by MithicSpirit)

@fluteyoshi debugedit is a dependency of base-devel, which is an implicit make dependency of every PKGBUILD, as per the wiki.

fluteyoshi commented on 2024-03-11 06:12 (UTC) (edited on 2024-03-11 06:12 (UTC) by fluteyoshi)

I noticed a bunch of "debugedit: command not found" errors during build on my machine, should debugedit be added as a build dependency?

txtsd commented on 2023-02-02 23:51 (UTC)

Updated the license and pushed the latest version.

MithicSpirit commented on 2023-02-02 20:13 (UTC)

@m4ksim it's very complicated (as legal things usually are), but in general the contributors maintain ownership over the code they write (unless otherwise stated; maybe there's something in github's ToS that does that?), so if you wish to relicense their code you'd need their permission. There's a lot more nuance to it than just that though.

m4ksim commented on 2023-02-02 18:30 (UTC)

Wait, so it isn't okay to change the license without the contributor's consent? Dang all those licensing thingies are very interesting

MithicSpirit commented on 2023-02-02 15:01 (UTC) used to be MIT, but switched to GPL-3.0 in mid-2020 (not even sure about the legality of that? did they get the consent of contributors?). Definitely should be fixed tho.

m4ksim commented on 2023-02-02 06:02 (UTC)

I think you are mistaken with the license.

Should be GPL-3.0

txtsd commented on 2022-07-25 04:13 (UTC)

Thanks! I pushed an update.