This is the mail archive of the
mailing list for the Cygwin project.
Re: pdksh installation
- From: "Elfyn McBratney" <elfyn-cygwin at exposure dot org dot uk>
- To: "cygwin" <cygwin at cygwin dot com>,"BB" <canofspam at att dot net>
- Date: Mon, 3 Mar 2003 16:32:29 -0000
- Subject: Re: pdksh installation
- References: <firstname.lastname@example.org> <Pine.GSO.email@example.com> <20030226200209.GA24694@redhat.com> <firstname.lastname@example.org>
> "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
> > >>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.
> > 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.
> > cgf
> 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
> I found out that someone was working on a cygwin package. I figured that
> 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
> 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
> reports prior to releasing a product to every Cygwin user. If a bug
> 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
> it's offical release though.
True. And I speak for the package maintainer here, of course. If there was a
problem with one of the package files that had not already been discovered
it would be nice to let him (me) know about it, if it hadn't already been
reported on the cygwin-apps mailing list during the testing phase.
elfyn at exposure dot org dot uk
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html