Thanks Pedro for the clarification.
Being a pure technological issue I dont have much sympathy for the Fedora
decision.
Regards,
Oliver
Am 14. August 2015 00:17:42 MESZ, schrieb "Pedro Côrte-Real"
<pe...@pedrocr.net>:
>On Thu, Aug 13, 2015 at 9:51 PM, Oliver Bedford
><oliver.bedf...@yahoo.de> wrote:
>> First of all I don't know what the term "copylib" means. I assume it
>> means you copy code from the library to your source code (and not
>> linking your code against the lib).
>
>Yep that's basically it.
>
>> If I further assume all the discussion is somehow related to patent
>infringement issues
>> then I don't understand how the way in which the library is bundled
>has any effect.
>
>There is no patent or copyright infringement at stake, legally
>everything is perfectly fine. This discussion is purely a technical
>one.
>
>> Overall I dont't understand the differences between dynamic, static
>> libraries, and copylibs and the effect of bundling/unbundling in this
>> context.
>
>So if you have a program (in this case darktable) and you want to use
>another piece of code (in this case rawspeed) you can do one of three
>things:
>
>1 - Just copy the code into your own code and treat it as a regular
>part of the program (what we currently do)
>2 - At compile time fetch a compiled version of the code and copy it
>in together with the rest of the program that you've compiled
>yourself. This is what a static library means.
>3 - At compile time add a reference to the library to your program.
>That reference will then be fetched from the filesystem when the
>program is ran and copied into the program by the operating system on
>startup (slight simplification). This is what a dynamic library means.
>
>The reason fedora wanted us to do 3 or potentially 2 is that they
>think it would make it easier for them to update their packages in
>case a security or other issue shows up in rawspeed. If we did 2 they
>would need to update the rawspeed package and then recompile
>darktable. If we did 3 they would just need to update the rawspeed
>package. The reason this is unworkable is that rawspeed doesn't have
>stable releases we can build on and there is no one available to start
>doing that work. The benefits are also quite elusive since we make
>very frequent releases (so are very responsive to bugs and security
>issues) and actively develop rawspeed ourselves (so would end up
>requiring rawspeed versions incompatible with rawstudio anyway).
>
>Cheers,
>
>Pedro
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
------------------------------------------------------------------------------
_______________________________________________
Darktable-users mailing list
Darktable-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-users
