Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <20000126163916.3624.qmail@web116.yahoomail.com> Date: Wed, 26 Jan 2000 08:39:16 -0800 (PST) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: next net release preliminary info To: J Shane Culpepper , cygwin-developers AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- J Shane Culpepper wrote: > I would suggest using rpm. Its been ported to cygwin and a great tool for > modular installation. Write an installer based on the rpm development libs > which can query for available packages much like redhat does. You could also > leverage from the up2date redhat modules written in perl and python (i > believe) for redhat distributions. Maybe this is too much work but it would > be a great distribution scheme. That way you can always get the latest > greatest modules for install. I'm a proud owner of the official 1.0 CD but > I'd love to be able to get certain things updated without having to always > build the modules I want. > > -Shane You know, I just hate for someone else to decide where the package is supposed to go for me. I much prefer the tarball method with a minimal directory, I.E., bin, man, info, share, etc. Then if I want to install an update of bash from bash-2.03 to bash-2.04.1 then I can: mkdir /install/bash-2.04.1 cd /install/bash-2.04.1 tar -zxvr bash-2.04.1-CygwinInstall.tar.gz and endup with /install/bash-2.04.1/bin and /install/bash-2.04.1/info Earnie. ===== Earnie Boyd Cygwin Newbies, please visit __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com