search

akeneo / pim-community-dev

[Community Development Repository] The open source Product Information Management (PIM)
http://www.akeneo.com
Other
953 stars 516 forks source link

Ghostscript: AGPL dependency #11466

Open dgomezleon opened 4 years ago

dgomezleon commented 4 years ago

Hello, Bitnami Engineer here,

As you may know, Bitnami's goal is to offer open source software up and running on any laptop, platform, cloud...

We are currently working on new Akeneo 4.0.0 (it would be great to have the latest documentation soon, because it includes a lot of new changes). We have some concerns with one of the new requirements:

Ghostscript executable must be at least 9.27

Ghostscript is under AGPL license from version 9.07 on, what is an issue to offer our cloud images on some cloud providers. We would like to understand why this is now a requirement and if there is a way to use a previous non-AGPL version.

Regards

jmleroux commented 4 years ago

@dgomezleon ,

Thanks for raising this issue. I will take some info and come back to you. Do not hesitate to ping me if needed.

dgomezleon commented 4 years ago

Thanks @jmleroux ,

Looking forward to your answer.

jmleroux commented 4 years ago

I am still looking to know if the licence is tied to the binary version. Do you know what is the licence for versions < 9.07?

dgomezleon commented 4 years ago

Previous versions are under GPL license. 9.07 is the first using AGPL license: https://www.ghostscript.com/doc/current/History9.htm#Version9.07

We use version 9.05 in our solutions.

dgomezleon commented 4 years ago

Hello @jmleroux ,

FYI, we have just release latest version 3 (3.2.44) without issues. Do you have any news about the requirements of the latest major version?

Regards

dgomezleon commented 4 years ago

Hello @jmleroux,

Do you have any news about the requirements of the latest major version? We would like to offer the latest version, however certain cloud marketplaces had restrictions (outside of our control) about not allowing AGPL software. In this case, what we try is to see if there's a way that the component can be swapped by an equivalent one. The goal is to give the widest possible distribution. If this is not possible, we cannot distribute it through the marketplaces (but will continue to do ourselves)

Regards