This is the mail archive of the
mailing list for the Cygwin project.
Re: pdksh installation
I am also looking forward to the release of a built-in ksh for
And, I can see that you wouldn't want to bug the maintainer with
frivilous questions that would delay what you are looking for.
However, I don't see a problem with making and playing in your
own mud-puddle. Here is what I have figured out so far:
You will need the bzip package installed so that you can run bunzip2
from the command line.
I believe that (others please jump in to correct if I am wrong) that
the Cyg Installer unpacks the package to the cygwin root directory
and then runs /etc/postinstall/<package_name>.sh.
What I did was unpack the bzip file to a scratch dir and then read
the <pkg>.sh to figure what post processing I had to do for my particular
If all of the above is Greek to you, then it probably would be best
to wait for the official release.
At 10:17 AM 2/27/03 -0600, BB wrote:
>"Christopher Faylor" <cgf-cygwin at cygwin dot com> wrote in message
>news:20030226200209 dot GA24694 at redhat dot com dot dot dot
>> On Wed, Feb 26, 2003 at 02:45:36PM -0500, Igor Pechtchanski wrote:
>> >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
>> >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.
>> Let me say again that I think it is a very bad idea for random people to
>> be installing the package before it is officially ready. As a package
>> maintainer, I would find questions or bug reports from newbies quite
>> annoying before the package is released.
>> "I saw you were digging a hole for your pool so I filled it with water.
>> How do I make the water nice and clear? It seems to be a little too
>> muddy for swimming."
>> If you want to sign on to help review packages then that is, of course,
>> welcome. However, if you have to ask how to install an .tar.bz2 file
>> then you have lots of learning to do before your insight will be useful.
>> I could even, if I was so inclined, pull the "off-topic" card for this.
>> Packages not included in the cygwin release are not what the cygwin
>> mailing list is supposed to be used for.
>> Of course, I wouldn't do something like that because I'm not that...
>> No. Wait a minute... Hmm.
>Well, I guess this would be the wrong mailing list for the question.
>Perhaps 'applications' would have been the correct place. But, I still
>think the question is a good on that deserves and answer. I'm sure that
>those that do know how to install the pre-release packages didn't always
>know how to do it.
>I was in the process of trying to build and modify pdksh for my own use when
>I found out that someone was working on a cygwin package. I figured that I
>might as will use the version that would eventually (maybe with mods) be
>incorporated into the Cygwin installation instead of my version. I fully
>understand that what pre-release means. Becaues I knew that that the
>setup.exe program did more than simply unzip the bz2, I asked the question.
>Maybe I shouldnt have specifically listed pdksh as my target product.
>I'm not sure I agree that a package maintainer would not want legitimate bug
>reports prior to releasing a product to every Cygwin user. If a bug report
>is simply an email or mailing list entry, what harm does it do. I would
>agree that questions about using the package might not be warranted prior to
>it's offical release though.
>Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting: http://cygwin.com/bugs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html