Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Original-Recipient: To: cygwin@cygwin.com Subject: Re: Copy to a CD and distribute to students Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-message-flag: Infected by Norwegian Cheese From: Andrew Markebo In-Reply-To: <20030407223033.GB332@redhat.com> (Christopher Faylor's message of "Mon, 7 Apr 2003 18:30:33 -0400") References: <20030407223033.GB332@redhat.com> Date: Tue, 08 Apr 2003 00:51:25 +0200 Message-ID: User-Agent: Gnus/5.090017 (Oort Gnus v0.17) Emacs/21.2 (gnu/linux) MIME-Version: 1.0 Ok sorry, should have written a bit clearer.. *sigh* why do we dig into stuff like this when we can play with the code? ;-) Ahh well, my first thoghts where that cygwin+source were bigger than 1 CD, therefore it might be easier for them going binaries only. How long will that last (the excellent size of today)? OTOH when cygwin climbs over 600 megs.. we are probably using DVD's ;-) /Andy | It's not a "hand it out if the student asks" situation. The best you | could hope for in this scenario is option b) above. That would mean | that you'd have to give the student something written with the source | code and archive the source for three years in case some student decided | they wanted to take you up on the offer. Every software company that I | am aware of who distributes code under the GPL uses option a) because | archiving everything and keeping track of what binary CD relates to what | sources is too much of a pain. -- From the other side of the screen it looked so easy - Tron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/