From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Contributing license information?
Date: Mon, 31 Oct 2011 14:27:00 -0000 [thread overview]
Message-ID: <20111031142720.GA23399@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4EAE31B5.3090404@cisra.canon.com.au>
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
next prev parent reply other threads:[~2011-10-31 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 1:01 Luke Kendall
2011-10-25 13:51 ` Corinna Vinschen
2011-10-25 20:07 ` David Sastre
2011-10-31 5:27 ` Luke Kendall
2011-10-31 14:27 ` Christopher Faylor [this message]
2011-11-01 2:18 ` Luke Kendall
-- strict thread matches above, loose matches on Subject: below --
2011-08-19 1:09 Luke Kendall
2011-08-19 12:04 ` Corinna Vinschen
2011-08-22 23:46 ` Luke Kendall
2011-10-20 3:49 ` Luke Kendall
2011-10-20 7:39 ` Corinna Vinschen
2011-10-20 7:49 ` Corinna Vinschen
2011-10-21 2:02 ` Luke Kendall
2011-10-21 8:59 ` Corinna Vinschen
2011-10-21 16:42 ` David Sastre
2011-10-21 17:36 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111031142720.GA23399@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).