X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: Setup.exe requirements [was RE: Cygintl-3.dll was not found]
Date: Thu, 10 Aug 2006 16:52:32 +0100
Message-ID: <000401c6bc94$fe3f70b0$a501a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <20060810133910.GB10459@trixie.casa.cgf.cx>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

On 10 August 2006 14:39, Christopher Faylor wrote:

> On Thu, Aug 10, 2006 at 10:00:19AM +0200, Tevfik Karag?lle wrote:
>> cgf wrote:
>>> Standards such as?  A pointer to a free installer which uses Windows
>>> standards and which will handle Cygwin's needs would be useful, e.g.,
>>> would NSIS meet your needs?  We've discussed using NSIS in the past.
>> 
>> Can anyone give me a qualified reference about the requirements of a
>> core cygwin environment ?  I would like to try to develop an NSIS
>> installer for it.
> 
> Huh?  setup.exe installs a "core cygwin environment" right now.
> What kind of reference would you be expecting other than the
> operation of the current installer?
> 
> cgf

  I imagine Tevfik just wants us to enumerate the things it needs to do:

1)  Allow package selection and handle dependencies, based on setup.ini
information and the content of the local package store.
2)  Create basic cygwin registry mountpoints if they don't already exist.
3)  Untar selected package tarballs in cygwin root directory when installing,
delete previously installed files when uninstalling.
4)  Run preuninstall and postinstall scripts as requested.
5)  Maintain suitable setup.db information for cygcheck to continue working.
6)  Optionally create desktop / start menu shortcuts.

  Does that cover all the essentials?

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/