X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,TW_CG X-Spam-Check-By: sourceware.org Message-ID: <4EAF56EB.9080301@cisra.canon.com.au> Date: Tue, 1 Nov 2011 13:18:19 +1100 From: Luke Kendall User-Agent: Thunderbird 2.0.0.21 (X11/20090302) MIME-Version: 1.0 To: CC: audit Subject: Re: Contributing license information? References: <4EA60A43.3050804@cisra.canon.com.au> <20111025135045.GA22635@calimero.vinschen.de> <20111025200701.GA6341@jethro.local.lan> <4EAE31B5.3090404@cisra.canon.com.au> <20111031142720.GA23399@ednor.casa.cgf.cx> In-Reply-To: <20111031142720.GA23399@ednor.casa.cgf.cx> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Christopher Faylor wrote: > 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 I don't know enough about setup.ini to understand why that's hard (my script can already do it), but I accept it. > and I'm not interested in modifying setup.exe > to deal with the new field. > > Although it sounds easy to me (since the info's not for setup and so setup should ignore the extra info), I don't know how setup's written, and you're the boss, so what you say, goes! > 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 > > Okay, that's blunt but quite clear. So we'll go ahead with the other approach. luke > -- > 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 > > -- 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