Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Tue, 17 Oct 2000 17:11:55 -0400
Message-Id: <200010172111.RAA14515@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: John DOT Wiersba AT medstat DOT com
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <03F4742D8225D21191EF00805FE62B9904B3F577@aa-msg-01.medstat.com>
	(message from John Wiersba on Tue, 17 Oct 2000 16:54:27 -0400)
Subject: Re: bugs in zip and bash
References:  <03F4742D8225D21191EF00805FE62B9904B3F577 AT aa-msg-01 DOT medstat DOT com>


> > Easy patch - feel free to try changing it yourself; you might surprise
> > yourself ;-)
> 
> Hmmm, I thought setup.exe was a windows-API program, so I didn't even think
> of trying to fix it.  Is it buildable under cygwin?  How can I get setup.exe
> to install the source (for any of the cygwin sub-packages)?

http://sources.redhat.com/cygwin/cvs.html

You'll have to build it all the first time, which takes a while, but
after that you'll only have to build src/winsup/cinstall.

Yes, it builds with cygwin.  I build it that way all the time.

> Well, "no clue" was a little strong.  I did figure out what they're supposed
> to do, but they certainly didn't seem to do it when I clicked on them!  For
> instance I'm looking at the full list now, but Prev/Curr don't make any
> difference that I can see, even though I have two .tar.gz files under
> latest/bash right now.

If both .tar.gz files have a YYYYMMDD `version' then they're both
"experimental" and setup will just pick the newer of the two.  It's
more for "install from internet" when a setup.ini is involved, as
setup.ini can control those buttons directly.

> This doesn't seem to work for me.  Or maybe I'm just misunderstanding what
> it really does.

You really need a setup.ini to make use of those buttons.

> This is good information.  I also have the the log files in with the
> downloaded .tar.gz files.

If you "download to current directory" they get put there instead of
the install root, since there is no install root in that case.

> As I mentioned, I had a few failures running setup.

Failures are different than wreaking havoc by selecting the wrong
setup options.

> One reason might be because I changed the mounts to /usr/bin and
> /usr/lib into symlinks.

Shouldn't matter.

> I also tried to install bash one time while it was running (oops!).

Yeah, that doesn't work.  It should let you re-install if you run
it again, after closing that bash window.

> setup.exe has also crashed a couple times when I've backed up to a
> previous screen.

*That* isn't supposed to happen.

> Sounds good.  Doesn't work for me.  Maybe I'll reinstall the whole thing.

No, try putting *just* the version of bash you want in the directory.
Like I said, If they both have yyyymmdd versions you may only see one
option.  Especially if there's also a setup.ini, which setup will use
*instead of* reading the directory, if it exists.

> It seemed like setup was trying to create /usr/bin but couldn't
> because I already had a symlink there.

That may be true, but it shouldn't stop the installation.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com