From: David Kastrup on
Hyman Rosen <hyrosen(a)mail.com> writes:

> On 3/25/2010 10:05 AM, David Kastrup wrote:
>> Licenses covering a work "as a whole" are hard to press
>> when the material they cover is functionally a drop-in
>> replacement of existing non-free libraries. That makes
>> "mere aggregation" a really good defense.
>
> This is completely wrong.

The legal council of the FSF is, as far as I can concern, of different
opinion than you are, and this opinion influences what kind of work they
decide to release under what kind of license.

So whether or not you agree with their reasoning, it is part of the
decisions they make with regard to licensing.

--
David Kastrup
From: Alexander Terekhov on

Hyman Rosen wrote:
[...]
> Similarly, mere aggregation is irrelevant to libraries which
> are statically linked into programs. Such a combined work is
> not a mere aggregation of the library and the other components.

Static linking is "mere aggregation" of (sub)programs with relocation
and symbol resolution done earlier than in the case of dynamic linking.

See also

http://www.rosenlaw.com/Rosen_Ch06.pdf
(Linking to GPL Software)

and

http://www.btlj.org/data/articles/21_04_04.pdf
(SOFTWARE COMBINATIONS UNDER THE GENERAL PUBLIC LICENSE)

regards,
alexander.

P.S. "Every computer program in the world, BusyBox included, exceeds the
originality standards required by copyright law."

Hyman Rosen <hyrosen(a)mail.com> The Silliest GPL 'Advocate'

P.P.S. "Of course correlation implies causation! Without this
fundamental principle, no science would ever make any progress."

Hyman Rosen <hyrosen(a)mail.com> The Silliest GPL 'Advocate'

--
http://gng.z505.com/index.htm
(GNG is a derecursive recursive derecursion which pwns GNU since it can
be infinitely looped as GNGNGNGNG...NGNGNG... and can be said backwards
too, whereas GNU cannot.)
From: Hyman Rosen on
On 3/25/2010 11:18 AM, Alexander Terekhov wrote:
> Static linking is "mere aggregation" of (sub)programs with relocation
> and symbol resolution done earlier than in the case of dynamic linking.

No, static linking results in a combined work since the
elements are chosen with intention and by design, much
as would be the case for stories in an anthology. Mere
aggregation corresponds to shipping a pile of books in
one box.
From: David Kastrup on
Hyman Rosen <hyrosen(a)mail.com> writes:

> On 3/25/2010 11:18 AM, Alexander Terekhov wrote:
>> Static linking is "mere aggregation" of (sub)programs with relocation
>> and symbol resolution done earlier than in the case of dynamic linking.
>
> No, static linking results in a combined work since the
> elements are chosen with intention and by design, much
> as would be the case for stories in an anthology. Mere
> aggregation corresponds to shipping a pile of books in
> one box.

It would appear that you are not familiar with the realities of dynamic
linking on UNIX-like operating systems. Dynamically linked libraries
(we are not talking about Windows DLLs here) are carefully versioned and
tend to become incompatible with their predecessors pretty regularly.
That's why you need to compile a program using dynamic libraries with
the corresponding header versions for the API versioning.

It is a quite special case to explicitly load a shared executable (and
call its entry points) for which not particular headers were used in the
preparation of the binary. I do not even know the library/system call
for that.

--
David Kastrup
From: Raffael Cavallaro on
On 2010-03-25 09:51:04 -0400, Hyman Rosen said:

> The FSF does not believe that the GPL is a poor fit for
> libraries.

The release of the Library GPL is an implicit recognition of the fact
that the GPL is a poor fit for libraries. Renaming it to the Lesser GPL
isn't likely to convince anyone old enough to remember, or intelligent
enough to do a little research.

warmest regards,

Ralph

--
Raffael Cavallaro