Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Wed, 26 Feb 2003 14:45:36 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: BB cc: cygwin AT cygwin DOT com Subject: Re: pdksh installation In-Reply-To: Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 26 Feb 2003, you (whoever you are) wrote: > I have read in the cygwin-apps list that pdksh is available. Until it is > officially announced and available in the package list, what is the correct > procedure for installing it? Can I use the setup program to install it? > > I guess this question applies to any new package that is not officially > released. This depends on who is releasing the package. Sometimes people have their own setup-aware mirrors, with the appropriate setup.ini file. Their announcements of packages then usually contain something like "To review, point your setup.exe to ". You can then use setup.exe to install the packages. The normal practice, however, is for people to provide the links to the .tar.bz2 (or .tar.gz) and setup.hint files directly. In this case, those reviewing do not use setup.exe to install and look over the packages, but they are supposed to know exactly what they are doing when they do that. Unless you fall into that category, I recommend you wait until the package is officially available. Alternatively, you could place yourself into that category (by looking over the source of setup.exe and figuring out exactly what it does in addition to unpacking the archives), and then repeat the procedure manually. It should be a bit easier to simply unpack the source package to /usr/src (since it doesn't *usually* involve any additional magic on the part of setup.exe), and build it yourself. Keep in mind that while the package is being reviewed, the source package *may* contain packaging errors. If you were asking about pdksh in particular, it should compile from the web sources () with the following patch: ============================================================================== --- ./misc.c-orig 2003-02-26 14:26:53.000000000 -0500 +++ ./misc.c 2003-02-26 14:27:00.000000000 -0500 @@ -118,7 +118,7 @@ Xcheck_grow_(xsp, xp, more) return xsp->beg + (xp - old_beg); } -const struct option options[] = { +const struct pdksh_option options[] = { /* Special cases (see parse_args()): -A, -o, -s. * Options are sorted by their longnames - the order of these * entries MUST match the order of sh_flag F* enumerations in sh.h. --- ./sh.h-orig 1999-05-13 13:07:58.000000000 -0400 +++ ./sh.h 2003-02-26 14:25:47.000000000 -0500 @@ -458,12 +458,12 @@ EXTERN struct env { #define OF_INTERNAL 0x08 /* set internally by shell */ #define OF_ANY (OF_CMDLINE | OF_SET | OF_SPECIAL | OF_INTERNAL) -struct option { +struct pdksh_option { const char *name; /* long name of option */ char c; /* character flag (if any) */ short flags; /* OF_* */ }; -extern const struct option options[]; +extern const struct pdksh_option options[]; /* * flags (the order of these enums MUST match the order in misc.c(options[])) ============================================================================== Hope this answers your question... Enjoy, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk! -- /usr/games/fortune -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/