X-Spam-Check-By:	sourceware.org
Message-ID:	<7124570.post@talk.nabble.com>
Date:	Wed, 1 Nov 2006 15:15:08 -0800 (PST)
From:	infoterror <infoterror AT fastmail DOT fm>
To:	cygwin AT cygwin DOT com
Subject:	RE: Setup.exe requirements [was RE: Cygintl-3.dll was not found]
In-Reply-To:	<001e01c6bcb5$31979d00$1702a8c0@itefixb>
MIME-Version:	1.0
X-Nabble-From:	infoterror AT fastmail DOT fm
References:	<58fb98730601070837k26ad68f5l AT mail DOT gmail DOT com> <43BFEFB9 DOT EA24C5B4 AT dessent DOT net> <5718434 DOT post AT talk DOT nabble DOT com> <003001c6bb9a$4e15b140$a501a8c0 AT CAM DOT ARTIMI DOT COM> <5732487 DOT post AT talk DOT nabble DOT com> <20060809210958 DOT GA3815 AT trixie DOT casa DOT cgf DOT cx> <002101c6bc53$07062af0$1702a8c0 AT itefixb> <20060810133910 DOT GB10459 AT trixie DOT casa DOT cgf DOT cx> <000401c6bc94$fe3f70b0$a501a8c0 AT CAM DOT ARTIMI DOT COM> <Pine DOT GSO DOT 4 DOT 63 DOT 0608101213460 DOT 408 AT access1 DOT cims DOT nyu DOT edu> <001e01c6bcb5$31979d00$1702a8c0 AT itefixb>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id kA1NFNu4023486

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/

- Raw text -