Re: BK MetaData License Problem?

> 
> until now the Linux kernel tree was distributed in a tarball that had a
> nice COPYING file in a very prominent spot. With BK the situation is
> different - and like i said in previous mails it's not BK's "fault", but
> BK's "effect" - and it's a situation that needs to be remedied, right?

Strictly speaking, isn't it a violation of the GPL for somebody to distribute a single file of any GPLed project, without attaching the COPYING file to it?

E.G. say somebody makes a CVS tree available via the web - you can download foobar.c without ever seeing the COPYING file.

John.