-
Notifications
You must be signed in to change notification settings - Fork 31
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
Linux Container and System.Drawing.Common Library Errors #69
Comments
ImageSharp is cross platform, and a really awesome project. |
@Jogai |
I have experience with the predecessor and followed development. Its really impressive what they did. (And i have huge respect for @JimBobSquarePants) As for helping that would be more an issue with time than anything else, but I'm in need of generating PDF's in a linux container so I might have to jump in at some point anyway. |
@richard-scryber Unfortunately I was not aware that your library does not run in a linux container. However, I absolutely need a library that runs in a linux container. I have invested time to change scryber.core from System.Drawing to SkiaSharp. The first tests have shown that the changes in the fonts area was successful. But for the adjustment in the Can you please give me some feedback on this issue? What's your plan. Can we tackle this issue together, or is it not a priority for you? On the other hand, I am forced to switch to another library, which I would find extremely unfortunate. |
Dear @richard-scryber It would be great to hear from you soon. |
Any updates on Linux compatibility? I would also be very interested in running Scryber under Linux, preferably in a container. I would also be willing to help out with that to the best of my abilities. Regarding the library, I would prefer not to use ImageSharp due to the licensing. |
What's wrong with the apache 2 license? (which would apply here: https://docs.sixlabors.com/articles/imagesharp.web/#license) |
Because the Apache 2 license only applies for "non-commercial" projects, which are fairly limited for certain applications, as outlined in the repository's LICENSE;
They've announced a license change about three years ago, and the uncertainty about what the licensing would look like (pricing, permissions, and so forth) had required us to move to alternatives instead. So in a way, ImageSharp is a bit of a hot topic here. |
That doesn’t apply to this library though? The new license is explicitly non viral so any consumers of this library, commercial or otherwise are subject to the Apache license due to the deferral clause in the license.
|
@EndOfTheSpline The first bullet point applies here and the second to all dependants of this project. I dont see a problem. |
@EndOfTheSpline - Just really starting to get back into this after a 6 month break. There is a beta package that supports net6.0 and net standard 2.0 uploaded to Nuget (6.0.0.8-beta as of now). I'm running on Mac, and working well. I've also pushed this as a blazor wasm app onto cloudflare pages as a static site - that is working awesomely! Linus should not now be an issue. Would love feedback! :-) Also getting this into a docker container would be a great thing. As for the license - I am no expert, but @JimBobSquarePants - really appreciate your input. At the moment my expectation is that as this license is open, and anyone using Scryber will have a transitive package dependancy on ImageSharp then it should be ok. @Jogai - your input is appreciated too. |
I have problems to run scryber in a .net 6 linux container.
The Installation the library
libgdiplus
does not seem to solve the problem.https://github.com/richard-scryber/scryber.core/blob/master/docs/libgdiplus.md
System.Drawing is a windows only library.
https://docs.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/6.0/system-drawing-common-windows-only
Recommended action is to migrate to one of the following libraries:
What is the meaning about this? Should we migrate scryber.core to SkiaSharp?
@richard-scryber or @VincentNikkelen If you want, I can try to do this migration.
By the way.
I think the culture info in the unit test should be defined otherwise some tests f.e. with datetime will failing in some
environments.
Or is there an other solution for this problem?
Thank you for your feedback.
Originally posted by @eoehen in #68
The text was updated successfully, but these errors were encountered: