Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Wed, 27 Mar 2002 21:21:57 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: How to create a ksh93 package... Message-ID: <20020328022157.GB4292@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <00c301c1d5e8$038b6300$f20114d5 AT muffin> <20020328000656 DOT GC2331 AT redhat DOT com> <3CA25F67 DOT 80608 AT ece DOT gatech DOT edu> <3CA25FAF DOT 6010904 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CA25FAF.6010904@ece.gatech.edu> User-Agent: Mutt/1.3.23.1i On Wed, Mar 27, 2002 at 07:11:27PM -0500, Charles Wilson wrote: >Charles Wilson wrote: >>I suggest that the ksh-specific binaries should just go into >>/usr/bin/ksh/ > >or maybe /usr/libexec/ksh/ That might be ok. At least it is hidden a couple of levels down in the directory structure. cgf