how to comply question

Tamas TEVESZ ice at extreme.hu
Wed Aug 5 15:45:50 CEST 2009


hello,

i'd like to get some advice in the following matter.

there's an open source project, which, as a part of it's build 
framework, relies on a couple of gpl tools (coreutils pieces, make, 
stuff like that). to make life easier for users, binaries of these  
tools for some not-so-fortunate platforms (dos, os/2 and the like -- 
you get the idea) are included in the source repository. it turns out 
that for some of the stuff, we don't even know or can find a location 
for a source package.

removing these binaries is thought to create a "support nightmare" of 
sorts, even with pointers and documentation stating "you need to get 
it, do so here and here". including source packages is somewhere in 
the source repo is partially possible (as said, for some binaries we 
don't know a source), but we still can't be perfectly sure (though a 
certain level of confidence is there) whatever sources we include 
will match the binaries we include - point is, we aren't really in the 
coreutils "business", just including them so our users don't have to 
be in the coreutils business either ;)

what would be the appropriate course of action to take? 

advice is much appreciated.

thanks,

-- 
[-]

mkdir /nonexistent




More information about the legal mailing list