Re: Enable usage of epswrite again

[Zdenek Dohnal]

Hi all,

IMHO it is allowed, but it brings more responsibilities than the pros in
most cases. The best course of action (if possible) would be to rewrite
your code to use the new Ghostscript API.

If that's not possible, contact Ghostscript developers, Ken Sharp and
Chris Liddell, on IRC channel #ghostscript (freenode.net server) and
talk about a possibilities how to solve it.

Downloading and customizing code on your own must be the last resort -
because by doing this, your code will depend by your specific
Ghostscript version you customized - which means, you will need to
bundle Ghostscript into your software to make it work in all environments.

Once you will start bundling Ghostscript, then you become responsible
for fixing Ghostscript issues your bundled code has - especially
security vulnerabilities. So you'll end up periodically updating your
bundled Ghostscript and backporting security fixes, which were applied
in the original project lately.

To sum it up, once you bundle, you will end up maintaining your
Ghostscript project, or you let it be with bugs and vulnerabilities in
your software. That's why it is a last resort.

Have a nice day,


Zdenek

On 2/14/21 7:08 PM, Jose E. Marchesi wrote:
> Hi Amit.
>
>> Hi Is there a way to download an open-source and change it to customize? We
>> need to download the Ghost script and try to rename one of the function
>> eps2write as epswrite (deprecated version) for our legacy programs to be
>> compatible with the newer version of ghost script In the middle releases,
>> the epswrite device was renamed as eps2write causing us to not being able
>> to upgrade to latest version
> That's perfectly allowed.  As free software, you are free to adapt it to
> your needs and to use and/or distribute the modified versions.
>
> See https://www.gnu.org/philosophy/free-sw.en.html
>
-- 
Zdenek Dohnal
Software Engineer
Red Hat Czech - Brno TPB-C

OpenPGP_signature
Description: OpenPGP digital signature