On 6/9/05, Kyrre Ness Sjobak <kyrre@xxxxxxxxxxxxxxxxxx> wrote: > man, 06.06.2005 kl. 10.22 skrev Jeff Pitman: > > On Monday 06 June 2005 15:48, condition terminal wrote: > > > OK then.. so how are the files and scripts used to control the > > > building of the rpms outside the specs excluded from the conditions > > > of the GPL? > > > > Think of beehive as an over-glorified cron system. If you use cron to > > do a daily checkout from CVS and build a system, that doesn't mean you > > need to release the source code to cron for every release of your > > software. You could even use some proprietary cron setup and still not > > be obligated to release it. > > -- > > -jeff > > Sorry for dup., hit send a bit to early... > > And then there is people building GPL software with Closed-Source tools > such as the MS compiler... Does that make MS obligated to release their > compiler as GPL? > > Just curious... > > That would be fun. > I bet the GPL police would be all over them in a heart beat. Provided the coplied software linked with any of the compiler libs, as happens with GCC (to my knowledge). ta -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-devel-list
