Scripting Installs? missing setup.hints

Michael Adler adler@glimpser.org
Thu Jan 31 08:22:00 GMT 2002


> The information is in the setup.ini file.  Eventually all info will be moved
> to setup.hints.
>
> >Is this the responsibility of the package maintainers?
>
> Yes.  If they feel like doing so.

If I create them, would you incorporate them?

> >How is the central setup.ini generated?
>
> With a perl script.

Fascinating. Is it in the CVS? It's not jumping out at me.

> >How could one roll their own?
>
> By writing a program.

That much I've figured out, but I appreciate these helpful suggestions.

The missing part was how to generate setup.ini without all the
setup.hints. I knew that you had to do it somehow, but I can't find it in
the CVS. So, should I chop up your setup.ini and give it back to you as
setup.hints (or just use locally)? or is your current solution better and
shareable?

Thanks,

Mike Adler




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



More information about the Cygwin mailing list