New comment by blacklightpy on void-packages repository

https://github.com/void-linux/void-packages/issues/48957#issuecomment-2021589562

Comment:
@iFoundSilentHouse But wouldn't that violate every GPL program?

What needs to be done in this case is to ensure that a non-free fork of Void should not distribute GPL software in it's repository. That is, if you are referring to the `helio-sequencer.xbps` file.

If that was the case, distributing GIMP on MS Store would mean MS Store would have to be open sourced.
GPL permits you to distribute the software. It is only concerned that the source code of whatever was compiled be provided. [In a way, I do think it is actually a violation, but even RMS hasn't decided on a strong answer to that].

It's not like XBPS depends on Helio, it's the Helio package that depends on XBPS. Besides, GPL does allow system libraries and the build system to be proprietary. The only condition is that a free compiler should also be able to link to the same system libraries.

**For example:**
Open Source App <-> Closed Source Pull Library <-> GPL Package.

In this case, it is not the pull library that is depending on the GPL Package, but the Open Source App is. In our case, Helio Sequencer is the Open Source App that needs JUCE.