This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: /setup.html please read - feedback desired
On Sat, 2001-11-03 at 13:22, Christopher Faylor wrote:
> On Sat, Nov 03, 2001 at 12:57:23PM +1100, Robert Collins wrote:
>
> Are we disagreeing about something? I am not sure anymore.
:]
> I was just reacting to Chuck's assertion that setup.hint is now the
> "normal" method not the "fallback" method for version handling. I don't
> agree with that.
I happen to agree with Chuck. All the metadata to drive the new setup
*can* be placed directly into setup.ini or setup.hint. I'm in favour of
simply saying "put it in setup.hint".
> As I've said repeatedly, I expect that setup.hint will eventually hold
> all of the information and setup.ini will be generated solely from this.
> After that happens, eventually, I expect that there will be a file in
> the package itself which contains this info and maybe setup.hint will
> disappear.
Correct.
> Right now most of the information is concentrated in setup.ini. It was
> a lot easier for me to manipulate all of the package info in setup.ini
> than it would have been to have it in 88 different directories. I expect
> this to change.
I've no objection to *you* editing setup.ini. I've an objection to new
maintainers doing *anything* directly to setup.ini. And the doco we are
writing is for *new maintainers* - like Kevin.
> to add 'prev' and 'curr' options unless version numbering is strange or
> there is a 'test' requirement.
Agreed.
Rob