From: Christian Boos Date: 2001-12-20T22:05:21+09:00 Subject: [ruby-talk:29106] Re: Ruby 'make' replacement (Re: stderr from external process?) On licensing issues... -----Original Message----- From: Phil Tomson [mailto:ptkwt@shell1.aracnet.com] Sent: Thursday, December 20, 2001 4:09 AM To: ruby-talk ML; undisclosed-recipients: ; Subject: [ruby-talk:29057] Re: Ruby 'make' replacement (Re: stderr from external process?) In article <3c210d85$0$62854$edfadb0f@dspool01.news.tele.dk>, MikkelFJ wrote: > > >The Torrent Workflow is a recently RAA posted workflow scheduler that is >quite useful for build framework. >Unfortunately it is GPL'ed, which makes it of limited use. On the positive >side, it is not difficult to copy the concept. > Why does it's being under GPL limit it's use? Unless you are planning for your 'make' replacement to be closed source, I don't see why GPL would limit it's use even in commercial environments. Phil ---------------- I unfortunately work for a closed-source company, but I firmly stand up for open software. I'm sure there are rational ways to make those both world cooperate rather than fight. The GPL simply has other goals in mind. Whatever the letter is, the spirit is that closed source is evil and should disappear. I can't buy into that, even if I admire free software, and its gift culture (btw. thank you matz! in case I've not already said it :) My 'rubuild' tool will be open source if anyone is interested in having it. I'll choose the Ruby license, as this choice won't prevent me to bundle this piece of software with the rest of our closed source software (that doesn't make sense, given what we are selling, but I want to have the option, just in case). -- Christian