This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: pdksh installation

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 <some web address>".  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 */

-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,
      |\      _,,,---,,_		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:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]