Date: Mon, 31 Oct 2011 10:27:20 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Contributing license information?
Message-ID: <20111031142720.GA23399@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4EA60A43 DOT 3050804 AT cisra DOT canon DOT com DOT au> <20111025135045 DOT GA22635 AT calimero DOT vinschen DOT de> <20111025200701 DOT GA6341 AT jethro DOT local DOT lan> <4EAE31B5 DOT 3090404 AT cisra DOT canon DOT com DOT au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4EAE31B5.3090404@cisra.canon.com.au>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Mon, Oct 31, 2011 at 04:27:17PM +1100, Luke Kendall wrote:
>Those are further reasons I think it's more elegant to add the license 
>info to the setup.ini file.  But is the setup.ini creation currently 
>automated?  If so there will be some occasions where the license info 
>can't be automatically updated (and will require some human thought  to 
>fill in details).
>
>What do you think?

I'm not interested in trying to figure out an automated way to add
a new field to setup.ini and I'm not interested in modifying setup.exe
to deal with the new field.

One of the above is a showstopper so you're going to have to do what
others have suggested and put the information in the packages.

cgf

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