-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Licensing question #1180
Comments
:-o do you know which dependency is under a CC-BY-NC-3.0 license ? |
okay panic over!!!
|
|
I tried to list the licenses used by raylib's code dependencies https://gist.github.com/ibilon/ca0630adc9eb512bdba6b072edc0b0f7, it's missing info about |
@jubalh @chriscamacho Most of those example resources were also available on previous raylib versions, actually they were created by two of my students and they give me the rights to use them. About the
|
I just want to note that I really take a lot of care on the licenses used on raylib sources (and external libraries) but thanks for letting me know if I you find any problem with any of them. @chriscamacho I'm also really concerned about license to allow commercial use. |
@ibilon thanks for the licenses compilation, if you don't mind I'll add that information on raylib Wiki. |
No problem of course 👍 |
Added information formatted in raylib Wiki |
Closing this issue. Feel free to reopen if there is any concern. |
I removed Android Also removed |
@raysan5 The problem is, our tools scan the whole tarball, if it finds incompatible license files it doesnt let us upload it to the repository. Would you mind creating something like a minimal tarball, which just contains raylib and excludes the examples? For some minimal systems that might be interesting anyways. So far the latest raylib is still not in openSUSE because of this.. :( |
@jubalh yeah, I see... those licenses are relative to the assets used on the examples... Actually most of those assets are contributions of my students, I proposed those CC-BY-NC licenses to them. Actually those files have been there for several versions, I only moved the LICENSE file there for better organization. How could I create a minimal tarball? Does it work a zipped file? What should/could I include? |
I'm also confused about this. My assumption is that before we just didn't have scripts to check for such cases.
I thought about having at the release page: https://github.com/raysan5/raylib/releases |
Actually that license was for a not-used testing asset (Duck.gltf), it was already removed on commit 5fb6155.
I can just remove examples directory from current |
@jubalh Actually, there could be some assets on examples that have no license file attached (usually coming from contributions). Could it suppose a problem? In that case I can just edit |
Awesome :)
Maybe some other distrubtions rely on the current tarball (and its checksum) already. So I wouldn't change the current tarball. But you could provide a new one Or releasing 3.0.1 with new changes, new changelog but still contaning examples but without the strange license. But in any case I think examples mostly make sense for regular uses (like on windows) that build raylib itself or include it in their own project. But for distrubtions who just want to build the library for users to use it dynamically the examples are not important. So generally having two tarballs, one complete and one without examples might make sense anyways.
Legally I'm not sure. But in our case it won't be a problem because the script wont detect it :D |
@jubalh Ok, just updated the 3.0.0 release, added Actually |
@raysan5 this is awesome news! Thanks a lot for doing this! Also the saving in file size is excellent, I guessed that would happen. |
One small question I would like to ask. Should I install all of those: |
@jubalh Nice! Cross-fingers! 😄 About the headers, actually, all of them can be installed. By default, I just install |
Okay, thanks for the info! :) |
https://build.opensuse.org/request/show/799028 by user jubalh + dimstar_suse - Switch to noexamples tarball as requested in: raysan5/raylib#1180 So we don't ship examples with various licenses that we don't install anyways. - Add raylib-3.0.0-noexamples.patch: dont try to install examples Raysan seems to have forgotten that. - Added missing development header files. - Update to 3.0.0: * All global variables from the multiple raylib modules have been moved to a global context state, it has several benefits, first, better code readability with more comprehensive variables naming and categorization (organized by types, i.e. CORE.Window.display.width, CORE.Input.Keyboard.currentKeyState or RLGL.State.modelview). Second, it allows better memory management to load global context state dynamically when required
request got accepted. We have raylib 3.0 now in openSUSE! |
@raysan5 why was there no noexamples tarball released for 3.5.0? |
@jubalh because I'm afraid there is no automatic system to generate it... |
Would you mind adding it? It's pretty good because of this licensing issue and the much smaller tarball :-) |
@jubalh ok, but... is there still some licensing issue? I reviewed it... EDIT: What should the .tar.gz contain? |
Even without license issue the smaller tarball is super nice to have for distros.
In April 2020 you said:
And that was quite fine. |
@jubalh I don't remember how it did it the last time... this time just updated the GitHub automatically generated .tar.gz archive: https://github.com/raysan5/raylib/releases/download/3.5.0/raylib-noexamples-3.5.0.tar.gz Please, let me know if it works ok. |
That tarball seems to be missing the CMakeLists.txt in the root directory. |
@jubalh Oh... sorry, I removed it with cmake directory... ok, reuploaded. Please note, I don't use and don't maintain CMake, it was a user contribution, I don't know if it currently works... |
Oh, I'm surprised to hear that. I remember that I contributed meson build files and removed them when CMake was added. I thought it would be the default for building on Linux now. What should I use as the official supported build method? |
@jubalh I created, use and maintain the plain Makefiles for all supported platforms. |
Does it also contain library versioning like the meson and cmake file did/do? |
@jubalh not sure if that's what you mean... I keep a RAYLIB_VERSION variable with current version that is used in some places... |
I mean library versioning which was discussed in:
|
@raysan5 Nevermind! I continue to use the CMake files :-) They still contain the library versioning. That's great! Hopefully they will always be in sync! Cheers! |
My submission of raylib 3.0.0 to openSUSE has been declined.
The bot sais:
So raylib now ships things with SCEA and CC-BY-NC-3.0 license? That's correct? Then I'll add them to the spec file.
The text was updated successfully, but these errors were encountered: