Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <3B8BA868.4070404@ece.gatech.edu> Date: Tue, 28 Aug 2001 10:19:20 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713 X-Accept-Language: en-us MIME-Version: 1.0 To: egor duda CC: Robert Collins , cygdev Subject: Re: Updated setup.ini with descriptions, categories, and dependencies References: <20010827004327 DOT A14852 AT redhat DOT com> <20010828134119 DOT A25382 AT cygbert DOT vinschen DOT de> <2022197257 DOT 20010828160649 AT logos-m DOT ru> <20010828142656 DOT C25382 AT cygbert DOT vinschen DOT de> <9824009784 DOT 20010828163702 AT logos-m DOT ru> <20010828150605 DOT F25382 AT cygbert DOT vinschen DOT de> <999004598 DOT 5646 DOT 3 DOT camel AT lifelesswks> <15228291410 DOT 20010828174823 AT logos-m DOT ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit egor duda wrote: > Hi! > > Tuesday, 28 August, 2001 Robert Collins robert DOT collins AT itdomain DOT com DOT au wrote: > > RC> Which brings up a suggestion: how about we rename the "cygwin" package > RC> to "libcygwin". This might reduce some of the "I installed cygwin" > RC> confusion. > > yes! and split it into 'libcygwin' (or 'cygwin-core') 'cygwin-utils' > (ahem, doesn't it yet look like i just love splitting packages? ;) ) > splitting openssh into ssh-client and ssh-server is a good thing too, i > believe. at least if we want to give user an option to choose what he > wants to install, we should try to provide as much granularity as > possible. Spliiting packages is okay, now that we've got categories. (Dang! I need to go update all my build scripts...) But, you need to be careful, as I discovered with xpm vs. xpm-nox, to keep at least one of your "new" packages with the same name as the "old" package. Otherwise, you get continual attempts to update/install the old one -- which may conflict with the new packages' files. e.g. OLD NEW ssh ssh-server ssh-clients ssh (perhaps empty? perhaps docs only) FWIW, I like what RH and Mandrake have been doing recently with libraries: package 'libfooN' contains /usr/lib/libfooN.so (runtime shared library and ldconfig-style symlinks). That way, you can have multiple major revisions of the shared lib installed -- libfoo0 and libfoo1, for instance. (in our case, /usr/bin/cygfoo0.dll and /usr/bin/cygfoo1.dll). Package 'libfoo-devel' contains the static lib and header files, as well as the devel-time symlinks for the most recent runtime-sharedlib package (Thus, in my example, the "current" version of libfoo-devel depends on libfoo1. In cygwin, this means libfoo-devel contains the implib for cygfoo1.dll) Then, package 'foo' contains docs, any executables that may be part of the 'package', and other "leftover" stuff. This works well with cygwin, because after "splitting" we'd still have a package named 'foo' to serve as the "update" for the old, monolithic 'foo' package. (side note: something I'd like to add to setup -- and I'll do it myself when I get a chance, so this isn't a whine -- is a button to "Skip All Uninstalled". I haven't installed irc, mutt, or squid -- and every time I want to update, say "ash", I have to deselect those three packages. With more and more packages added all the time, there's going to be more packages I just don't want to install; worse, they will now be hidden amonst various sub-categories...) --Chuck