This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Setup.exe requirements [was RE: Cygintl-3.dll was not found]
- From: infoterror <infoterror at fastmail dot fm>
- To: cygwin at cygwin dot com
- Date: Wed, 1 Nov 2006 15:15:08 -0800 (PST)
- Subject: RE: Setup.exe requirements [was RE: Cygintl-3.dll was not found]
- References: <58fb98730601070837k26ad68f5l@mail.gmail.com> <43BFEFB9.EA24C5B4@dessent.net> <5718434.post@talk.nabble.com> <003001c6bb9a$4e15b140$a501a8c0@CAM.ARTIMI.COM> <5732487.post@talk.nabble.com> <20060809210958.GA3815@trixie.casa.cgf.cx> <002101c6bc53$07062af0$1702a8c0@itefixb> <20060810133910.GB10459@trixie.casa.cgf.cx> <000401c6bc94$fe3f70b0$a501a8c0@CAM.ARTIMI.COM> <Pine.GSO.4.63.0608101213460.408@access1.cims.nyu.edu> <001e01c6bcb5$31979d00$1702a8c0@itefixb>
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/