IRC channel logs

<ArneBab>lechner: I’d think GPL would come in at the minimum when you call some procedure from the go file, because then you have intimate data communication and it’s not a system library.

<lechner>ArneBab: Thanks! I just released two C files that become shared objects under the LGPL. What would you have done, please? https://codeberg.org/lechner/guile-pam/commit/cd4b54b89db2e20259a8739e2d9328c013f9d2d4

<cns>can someone tell me how guile does variable resolution or should I check the source?

<cns>nvm i get it now

<dsmith>Arrr

<dsmith>sneek, botsnack

<sneek>:)

<ArneBab>lechner: nice! it depends on what you want to achieve. If you want guile-pam to be usable in proprietary programs (for example games) or if you want to open a path to merge that into Guile itself (which Guile uses because it competes with lax licensed languages, and allowing proprietary programs to use it while requiring changes within guile to stay free is the best strategy for that), then LGPL is the way to go.

<ArneBab>lechner: there are details to that: GNU readline has been the cause for several programs to become Free Software, because they wanted to use readline and the only way to get that was to become Free Software. That’s why readline under GPL is the right path forward. For many years there was nothing comparable, so this gave Free Software a serious edge over proprietary software.

<ArneBab>So if there’s no competition in that space, GPL or AGPL is the way to go. If there are many similar programs already, LGPL can be the better strategic choice.

IRC channel logs

2026-09-19.log