Combining copyrights on Erlang source files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A question occurred to me after doing a review recently about whether
Erlang source is compiled and linked together like C source or whether
the source files remain separate like, say, Python.  The issue is an
Erlang package where some source files are LGPLv3+ but one is GPLv2+.  I
took the safe route and assumed that the final result is GPLv3+, but
unfortunately I don't quite know enough about either Erlang or the
actual legal threshold at which the sources are considered to be
commingled.  When I look at the compiled application, it looks as if
each of the .erl files gets turned into a .beam file, and those files
look to be kept separate in the final package.

The ticket, with a package you can build, is at
https://bugzilla.redhat.com/show_bug.cgi?id=502991

 - J<

_______________________________________________
Fedora-legal-list mailing list
Fedora-legal-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-legal-list

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Gnome Users]     [KDE Users]

  Powered by Linux