From: =?iso-8859-1?Q?Tevfik_Karag=FClle?= <tevfik AT itefix DOT no>
To: <cygwin AT cygwin DOT com>, "'Dave Korn'" <dave DOT korn AT artimi DOT com>
Subject: RE: Setup.exe requirements [was RE: Cygintl-3.dll was not found]
Date: Thu, 10 Aug 2006 23:59:18 +0200
Message-ID: <003701c6bcc8$3b846010$1702a8c0@itefixb>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
In-Reply-To: 
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit

 I don't know how to switch from digest mode to normal mode.
That's why I think this mail is a little bit out-of-sync. Sorry about that.

After feedback from cgf, I have scanned setup.ini for packages and
their dependencies. 54 of 797 packages are qualified for Base either
directly or indirectly:

_update-info-dir
alternatives
ash
base-files
base-passwd
bash
bzip2
coreutils
crypt
cygutils
cygwin
cygwin-doc
diffutils
editrights
findutils
gawk
gdbm
grep
groff
gzip
less
libbz2_1
libcharset1
libgdbm
libgdbm-devel
libgdbm3
libgdbm4
libiconv
libiconv2
libintl
libintl1
libintl2
libintl3
libncurses5
libncurses6
libncurses7
libncurses8
libpcre0
libpopt0
libreadline4
libreadline5
libreadline6
login
man
mktemp
ncurses
run
sed
tar
termcap
terminfo
texinfo
which
zlib
 
I will develop an NSIS package which creates registry
Mount points, untar packages above and run the
Postinstall script. Any suggestions including naming
are welcome.

Rgrds Tev 

> -----Original Message-----
> From: Tevfik Karagülle [mailto:tevfik AT itefix DOT no] 
> Sent: Thursday, August 10, 2006 9:43 PM
> To: 'cygwin AT cygwin DOT com'; 'Dave Korn'
> Subject: RE: Setup.exe requirements [was RE: Cygintl-3.dll 
> was not found]
> 
> Thanks.
> 
> According to the setup.exe default package information, 
> Following 41 packages forms 'a core cygwin environment':
> 
> ---------------------------
> Alternatives ash base-files base-passwd bash coreutils cygwin 
> cygwin-doc diffutils editrights findutils gawk gdbm Grep gzip 
> libgdbm lidgdbm-devel libgdbm3 libgdbm4
> libncurses5 libncurses6 libncurses7 libncurses8 libreadline4
> Libreadline5 libreadline6 login man ncurses run sed Tar 
> termcap terminfo which zlib cygwin-doc man gawk Termcap zlib
> ---------------------------
> 
> 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.
> 
> Rgrds Tev
> 
> > -----Original Message-----
> > From: Igor Peshansky [mailto:pechtcha AT cs DOT nyu DOT edu]
> > Sent: Thursday, August 10, 2006 6:17 PM
> > To: Dave Korn
> > Cc: cygwin AT cygwin DOT com
> > Subject: Re: Setup.exe requirements [was RE: Cygintl-3.dll was not 
> > found]
> > 
> > On Thu, 10 Aug 2006, Dave Korn wrote:
> > 
> > > 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?
> > 
> > 7)  Run preremove scripts on uninstalls.
> > 8)  Allow installing package sources.
> > 	Igor
> > -- 
> > 				http://cs.nyu.edu/~pechtcha/
> >       |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | 
> > igor AT watson DOT ibm DOT com
> > ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. 
> > (name changed!)
> >      |,4-  ) )-,_. ,\ (  `'-'		old name: Igor 
> Pechtchanski
> >     '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
> > 
> > "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu 
> t'en rends 
> > compte."
> > "But no -- you are no fool; you call yourself a fool, there's proof 
> > enough in that!" -- Rostand, "Cyrano de Bergerac"
> > 
> 


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