Re: A simple mistake (was Re: Should we ship KDE in hamm?)
Raul Miller wrote:
> Dynamic linking is like static linking in that in either case the program
> won't run without the library. Dynamic linking is unlike static linking
> in that the linkage is created every time the program runs, rather than
> every time the prgram is linked. Also, we generally do not make it a
> practice of shipping unlinked .o files, arranging to statically link
> them in the user's machine.
>
> That's about the extent of the technological differences..
>
> What you're ignoring is that we introduce a very strong association
> between the binaries and the libraries, using dpkg. This, in
> combination with some of the other associations (our testing process,
> the documentation on the program, and of course the way we build the
> package in the first place) make it very obvious that we intended that
> qt be used to make kde work.
Plus, in the case of C++, the header files actually *have* code not just
prototypes so even if dynamic linking were allowed, there would still be a
problem with mixing actual code contained in the binary and coming from a
non GPLed source.
Luis.
--
Luis Francisco Gonzalez <luisgh@cogs.susx.ac.uk>
PGP Fingerprint = F8 B1 13 DE 22 22 94 A1 14 BE 95 8E 49 39 78 76
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: