Tevfik Karagülle wrote:
>
> In the first phase, I can think of producing a monolithic
> installer for the core environment performing tasks
> below:
>
> - Create basic cygwin registry mountpoints
> - untar packages
> - run the postinstall script
> - Create start menu items and shortcuts (optional)
> - maintain setub.db (how?)
>
> Would that be a valid cygwin installation ?
>
> Second phase could be to introduce upgrade functionality.
>
This is an excellent idea. I spoke to a friend via phone two nights ago who
added another request: perhaps, if packages are listed in an updated, there
can be some explanation visible of what they are, possibly even a column in
the interface:
package-name (other config data) Libraries for input/output and
intoxication.
?
--
View this message in context:
http://www.nabble.com/Cygintl-3.dll-was-not-found-tf869884.html#a7124570
Sent from the Cygwin Users mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
