Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-22 Thread Jeff Licquia
On Mon, 2002-07-22 at 09:49, Boris Veytsman wrote: > > From: Jeff Licquia <[EMAIL PROTECTED]> > > > My /usr/local/bin can > > > be NFS-exported to hundreds of computers. Even my box can have > > > hundreds logins there. > > > > Yes, but in the former case, you are distributing the program to > >

Re: defining 'distribution' (Re: A few more LPPL concerns)

2002-07-22 Thread Jeff Licquia
On Mon, 2002-07-22 at 10:22, Joe Moore wrote: > Jeff Licquia wrote > > On Sun, 2002-07-21 at 23:10, Boris Veytsman wrote: > >> My /usr/local/bin can > >> be NFS-exported to hundreds of computers. Even my box can have > >> hundreds logins there. > > > > Yes, but in the former case, you are distri

Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-22 Thread Boris Veytsman
> From: Jeff Licquia <[EMAIL PROTECTED]> > Date: 22 Jul 2002 00:47:39 -0500 > > On Sun, 2002-07-21 at 23:10, Boris Veytsman wrote: > > Exactly. I really do not see the difference between running a program > > from /usr/local/bin or /afs/whatever/bin/. What is the difference > > between AFS and NF

Re: defining 'distribution' (Re: A few more LPPL concerns)

2002-07-22 Thread Joe Moore
Jeff Licquia wrote > On Sun, 2002-07-21 at 23:10, Boris Veytsman wrote: >> > From: Jeff Licquia <[EMAIL PROTECTED]> >> > Date: 21 Jul 2002 22:59:26 -0500 >> > >> > It's crucial to your point, therefore, that there not be a >> > distinction between running the program from /usr/local/bin or >> > /a

Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-22 Thread Lynn Winebarger
On Sunday 21 July 2002 22:59, Jeff Licquia wrote: > On Sun, 2002-07-21 at 22:40, Boris Veytsman wrote: > > I think that a sysadmin that put > > a changed copy of latex.fmt in the $TEXFORMATS directory to be used by > > his users, *distributes* a changed LaTeX. You think he does not; the > > problem

Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-22 Thread Edmund GRIMLEY EVANS
Jeff Licquia <[EMAIL PROTECTED]>: > > When I execute a program, this is not a distribution. When I allow > > others to execute it, I distribute it -- even if there is no actual > > copying of bits between magnetic media. > > Actually, it's not clear that this is true. For example, technically a

Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-22 Thread Jeff Licquia
On Sun, 2002-07-21 at 23:10, Boris Veytsman wrote: > > From: Jeff Licquia <[EMAIL PROTECTED]> > > Date: 21 Jul 2002 22:59:26 -0500 > > > > It's crucial to your point, therefore, that there not be a distinction > > between running the program from /usr/local/bin or /afs/whatever/bin. I > > think w

Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-21 Thread Boris Veytsman
> From: Jeff Licquia <[EMAIL PROTECTED]> > Date: 21 Jul 2002 22:59:26 -0500 > > It's crucial to your point, therefore, that there not be a distinction > between running the program from /usr/local/bin or /afs/whatever/bin. I > think we've shown that this isn't the case, since a sysadmin does not

Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-21 Thread Jeff Licquia
On Sun, 2002-07-21 at 22:40, Boris Veytsman wrote: > > From: Jeff Licquia <[EMAIL PROTECTED]> > > Date: 21 Jul 2002 20:34:32 -0500 > > > You're right, and there may be software you can't install on your AFS > > drive in this instance, because you're "distributing" software to those > > thousand co

Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-21 Thread Boris Veytsman
> From: Jeff Licquia <[EMAIL PROTECTED]> > Date: 21 Jul 2002 20:34:32 -0500 > You're right, and there may be software you can't install on your AFS > drive in this instance, because you're "distributing" software to those > thousand computers. This is irrespective of whether any of those > thousa

Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-21 Thread Jeff Licquia
On Sun, 2002-07-21 at 20:18, Boris Veytsman wrote: > > From: Jeff Licquia <[EMAIL PROTECTED]> > > Date: 21 Jul 2002 18:07:50 -0500 > > > > On Sun, 2002-07-21 at 16:49, Boris Veytsman wrote: > > > This is the root of our disagreement. I think that a sysadmin that put > > > a changed copy of latex.f

Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-21 Thread Boris Veytsman
> From: Jeff Licquia <[EMAIL PROTECTED]> > Date: 21 Jul 2002 18:07:50 -0500 > > On Sun, 2002-07-21 at 16:49, Boris Veytsman wrote: > > This is the root of our disagreement. I think that a sysadmin that put > > a changed copy of latex.fmt in the $TEXFORMATS directory to be used by > > his users,

Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-21 Thread Jeff Licquia
On Sun, 2002-07-21 at 16:49, Boris Veytsman wrote: > > Date: Sun, 21 Jul 2002 14:32:39 -0700 (PDT) > > From: Mark Rafn <[EMAIL PROTECTED]> > > > > > Suppose I take a GPL'ed program, change it and put the closed version > > > (sans sources) on my own machine. I did not violate GPL yet. Now > > > su

Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-21 Thread Nick Phillips
On Sun, Jul 21, 2002 at 05:49:34PM -0400, Boris Veytsman wrote: > This is the root of our disagreement. I think that a sysadmin that put > a changed copy of latex.fmt in the $TEXFORMATS directory to be used by > his users, *distributes* a changed LaTeX. You think he does not; the > problem with yo

Re: defining "distribution" (Re: A few more LPPL concerns)

2002-07-21 Thread Boris Veytsman
> Date: Sun, 21 Jul 2002 14:32:39 -0700 (PDT) > From: Mark Rafn <[EMAIL PROTECTED]> > > > Suppose I take a GPL'ed program, change it and put the closed version > > (sans sources) on my own machine. I did not violate GPL yet. Now > > suppose that I make the drive NFS-exportable and encourage my pa

defining "distribution" (Re: A few more LPPL concerns)

2002-07-21 Thread Mark Rafn
> > Note that in the above, `distribution' of a file means making the file > > available to others by any means. This includes, for instance, > > installing the file on any machine in such a way that the file is > > accessible by users other than yourself. > > From: Mark Rafn <[EMAIL PROTECTED]>