X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Grant Edwards <grante AT visi DOT com>
Subject:	Re: Pointers on Making a Cygwin CD (including source)?
Date:	Thu, 8 Jan 2009 00:23:16 +0000 (UTC)
Lines:	54
Message-ID:	<gk3h1k$c0k$1@ger.gmane.org>
References:	<gk3afp$ocb$1 AT ger DOT gmane DOT org> <49653425 DOT 3070509 AT cygwin DOT com>
Mime-Version:	1.0
User-Agent:	slrn/pre0.9.9-102 (Linux)
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 2009-01-07, Larry Hall (Cygwin) <reply-to-list-only-lh AT cygwin DOT com> wrote:
> Grant Edwards wrote:
>> I need to put a Cygwin snapshot on CD[*].
>> 
>> To that end I've been searching the mailing list archive. So
>> far the scripts wirtten by Vin Shelton look like they're
>> awfully close to what I want.
>> 
>>   http://www.Cygwin.com/ml/Cygwin/2007-03/msg00606.html
>
> This link goes nowhere for me.

Doh!  My spell-checker capitalized Cygwin.  It should be

  http://www.cygwin.com/ml/cygwin/2007-03/msg00606.html

> The Cygwin DLL is meant to be backward compatible through the
> 1.5 series.  There will, of course, be a difference moving
> from 1.5 to 1.7.  After that, later 1.7 releases will be
> compatible with earlier ones.  And by compatible, I mean
> binary compatible.  No rebuild necessary.  If you find this is
> not the case with 1.7, then that would be good to report.
> Since 1.5 is a dead end, it doesn't make allot of sense to
> report these kinds of problems for it.  Of course, as you
> note, other packages aren't necessarily compatible through all
> their versions or even their minor version bumps.  If you need
> to support a particular set of Cygwin tools, it can make sense
> to lock the set you're working with.  Of course, you'll still
> need to contend with users that already may have Cygwin
> installed and the version conflicts there.

Users who already have Cygwin installed are probably savvy
enough to build the tools from sources.  If that doesn't work
then they're out of luck, and should just do things right and
install Linux.

> And, as you noted, you need to distribute the source of your
> application

I don't see what my application has to do with anything.  Just
because I compile an application with gcc, that doesn't place
the application under the GPL.

> along with that for the Cygwin DLL and the tools you're
> distributing to comply with the GPL, but I expect you already
> know this.

I'm aware that we'll need to distribute sources for Cygwin and
the other GPL'ed tools we're distributing.

-- 
Grant Edwards                   grante             Yow! I'm wet!  I'm wild!
                                  at               
                               visi.com            


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -