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 Date: Mon, 19 Nov 2001 20:59:24 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: -src package standard: proposal #5 and #5a Message-ID: <20011120015924.GA9068@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20011120010754 DOT GB8354 AT redhat DOT com> <004d01c17161$4f0a5c50$b09d3fcb AT itdomain DOT net DOT au> <3BF9B191 DOT 8FBDAA45 AT yahoo DOT com> <005901c17163$4db36cf0$b09d3fcb AT itdomain DOT net DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005901c17163$4db36cf0$b09d3fcb@itdomain.net.au> User-Agent: Mutt/1.3.23.1i On Tue, Nov 20, 2001 at 12:33:06PM +1100, Robert Collins wrote: >----- Original Message ----- >From: "Earnie Boyd" > >> Hmm... Why not just simply create an "All" category that all packages >> automagically go to? That could be done with the setup.ini script >> couldn't it? That should suffice for the short and even long terms. > >Because packages inevitably will conflict with each other. Say someone >provides vim compiled for X11. What happens if both vims are installed? Ok, >so that can be handled via symlinks, but there are corner cases, that grow >more frequent as the package list gets bigger. Ok, so call it "Most". Or "Almost All". Or "Major". I still don't see a reason to invent a whole other classification system. And, now that I think of it, you're actually anticipating that there will be a case where we'll have two executables called "vim" in the cygwin distribution? I guess I'm having a hard time imaginging that. cgf