Programming

20019 readers

267 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

snowe

Ategon

[email protected]

Licenses are boring but you really need one! (distractedmind.home.blog)

submitted 4 days ago by snaggen to c/programming

29 comments fedilink hide all child comments

It seems people have a hard time understanding the implications of licenses, so I have written a something to help with that.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 4 days ago* (last edited 4 days ago) (1 children)

If you statically link against an LGPLed library, you must also provide your application in an object (not necessarily source) format, so that a user has the opportunity to modify the library and relink the application.

Yeah, I think this is the hard part with Go. I've never seen anyone do anything with objects in Go. Everything is compiled into 1 binary, often statically linked. I'm not sure it's possible to build a Go binary by using object files.

[–] JackbyDev 1 points 4 days ago

So, you could release the source but with the standard "all rights reserved" of copyright and let people compile it with a different version of the LGPL lib, but not let them modify or redistribute the proprietary Go code you've written to use it. It sounds counterintuitive because the source is "available" but this is how proprietary JavaScript code works in browsers to. It's there, you can read it, but it doesn't automatically mean you can "do" anything with it.

So yeah, distribute your Go binary with access to your Go code and instructio on how to compile it and you should be good, unless I'm missing something obvious.