Re: Bug#296369: ITP: spin -- Powerfull model checking and softwareverification tool
(Why do you refuse to set a proper From: header? Among dozens of Johns
and Daves and Harries, it's quite hard to take someone calling himself
"OSS" seriously ...)
On Wed, Feb 23, 2005 at 12:53:00PM -0700, OSS wrote:
> >"LUCENT, at its sole discretion, may from time to time publish a revised
> >and/or new version of this Agreement (each such revised or new version
> >shall carry a distinguishing version number) which shall govern all copies
> >of Licensed Software downloaded after the posting of such revised or new
> >version of this Agreement."
> >which seems to say that the license may change or terminate at Lucent's
> >whim at any time. This means that whoever is distributing this must be
> >on constant license watch, in order to update the license or pull the
> >software from the archive if the license changes or is revoked. Is it
> >really a good idea to distribute such a time-bomb?
> Why would a term that only comes into play for software downloaded AFTER
> the change be a concern to software downloaded & redistributed before the
> change? Is this any different than Foo Inc. licencing App A v 1.0 under the
> GPL and releasing App A v1.1 under a clone of a CA EULA and stopping their
> distribution of App A v1.0?
1. I download the software, under the above license, and put it on my FTP
2. The license changes; it now says "redistribution of any kind is prohibited".
3. You mirror my FTP server. (I can still send it to you, since I'm under
the original license.)
4. You make your mirror available as an FTP server.
You have the new license, since you downloaded it after the license
revision. Your redistribution of the software violates the license.
It may be very hard to notice this, though, if what you're mirroring
is the non-free archive in whole: you can't assume much about non-free,
but you should at least be able to mirror it safely.