You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, if I include the package in the commercial project, not providing the source code, it seems to cause a very serious problem.
I don't care if TimSort is included, I really want this package to be used in commercial projects.
Of cause I can copy the source codes to my project, then delete the TimSort files. But that will make it difficult to sync to the newest version.
The text was updated successfully, but these errors were encountered:
As a special exception, the copyright holders of this library give you
permission to link this library with independent modules to produce an
executable, regardless of the license terms of these independent modules,
and to copy and distribute the resulting executable under terms of your
choice, provided that you also meet, for each linked independent module,
the terms and conditions of the license of that module. An independent
module is a module which is not derived from or based on this library. If
you modify this library, you may extend this exception to your version of
the library, but you are not obligated to do so. If you do not wish to do
so, delete this exception statement from your version.
Now, that said, on reflection I would like to keep the Redzen licensing clean and simple, and therefore I may remove Timsort from this library (and perhaps place it in some other package).
Another possibility here is that the recently proposed split of the Redzen.Random could happen sooner, and maybe that would work for you too?
So, if I include the package in the commercial project, not providing the source code, it seems to cause a very serious problem.
I don't care if TimSort is included, I really want this package to be used in commercial projects.
Of cause I can copy the source codes to my project, then delete the TimSort files. But that will make it difficult to sync to the newest version.
The text was updated successfully, but these errors were encountered: