> > 1) Oracle Corp. builds their database for Linux on a Linux system.
> > 2) Said system comes with standard header files, which happen in this case to
> > be GPL'd header files.
> > 3) Oracle Corp.'s database becomes GPL.
> >
> > There's not a court in the civilised world that would uphold the GPL in that
> > scenario.
>
> Yes but the concern is the USA 8)
Pardon me, but what does "Oracle Corp.'s database becomes GPL" mean in the
above 3)? (I'm asking to you since you seem to agree). Even if the
database is found to be linked with a GPLed piece of SW, this doesn't make
it (the database) GPLed, it just breaks Oracle's licence on the GPL SW.
They only have to recompile their program against non-GPLed code (e.g.
rewrite that part from scratch) and redistribute it. That's not like
everyone going to Oracle and say "Your SW is now GPLed, hand me the Source.
Resistance is Futile." ... GPL has a viral behaviour iff you want to
keep using the GPLed part that you included, or am I missing something?
.TM.
--
____/ ____/ /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / / ESI s.r.l.
_____/ _____/ _/ Colombo@ESI.it
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/