codito, Polish
@codito@mas.to avatar

Genuine question to maintainers and (not only) community: how licensing works when it comes to tools delivered as executable binary?

Context: package A has licence and © info. Package B bundles its dependencies. End user doesn't see A's credits when using B 🤔.

Crell,
@Crell@phpc.social avatar

@codito At least in theory, B is supposed to include "uses A under the LGPL" (or similar) in its credits. I'm not sure if that's a strict legal requirement, but it's at the very least good manners.

A fair number of proprietary apps do that for LGPL/MIT code they use, though of course they bury it deep in menus somewhere.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • opensource
  • ngwrru68w68
  • rosin
  • GTA5RPClips
  • osvaldo12
  • love
  • Youngstown
  • slotface
  • khanakhh
  • everett
  • kavyap
  • mdbf
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • megavids
  • InstantRegret
  • normalnudes
  • tacticalgear
  • cubers
  • ethstaker
  • modclub
  • cisconetworking
  • Durango
  • anitta
  • Leos
  • tester
  • provamag3
  • JUstTest
  • All magazines