Mail Archives: cygwin/2000/10/17/17:00:59
Thanks for your reply to the real substance of my original post. Somehow
the email tagging thing seems to have struck a chord for most others...
> -----Original Message-----
> From: DJ Delorie [mailto:dj AT delorie DOT com]
>
> > 5) I'm totally lost with the setup.exe GUI on the screen that says
> > "Select packages to install".
>
> > a) It has this same message even if I'm only downloading tarballs to
> > my local machine from the net.
>
> I assume you want it to say "Select packages to download", right?
Right.
> 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)?
> > b) I have no clue when/how/why I'm supposed to use the Prev/Curr/Exp
> > and Full/Part buttons.
>
> Then you probably don't need to use them. Seriously, a Help button is
> on the todo list, but I've gotten surprisingly little complaints about
> that dialog.
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.
> Prev/Curr/Exp chooses the previously stable, current stable, or
> experimental versions of all packages (if available).
This doesn't seem to work for me. Or maybe I'm just misunderstanding what
it really does.
> Full/Part
> toggles between a full listing of package, or a partial listing
> showing only those setup expects to change.
Yes, this makes sense now.
> /etc/setup/installed.db lists all installed packages.
> /etc/setup/*.lst.gz are used for uninstalling old packages before
> installing new versions.
>
> setup.log* contain a terse and full log of the setup. Save these if
> you have problems with setup, otherwise you can delete them. They are
> in / so they're easy to find (if you're having problems, we don't want
> finding these to be one of them).
>
> setup.ini is in with the downloaded .tar.gz files because it is part
> of the ftp mirror.
This is good information. I also have the the log files in with the
downloaded .tar.gz files.
> > Can I delete all of them?
>
> Not the ones in /etc/setup, but you can delete the others.
More good information.
> > e) A help screen for setup.exe would be good. I couldn't seem to
> > find the right info on the cygwin web page.
>
> There isn't any help yet. Most people don't have problems with setup;
> it's very hard to do something bad with setup.
As I mentioned, I had a few failures running setup. One reason might be
because I changed the mounts to /usr/bin and /usr/lib into symlinks. I also
tried to install bash one time while it was running (oops!). setup.exe has
also crashed a couple times when I've backed up to a previous screen.
> Run setup. Select "Full" in the chooser dialog. Click on the bash
> version until you get to the one you want. Continue.
Sounds good. Doesn't work for me. Maybe I'll reinstall the whole thing.
> Setup should never use /usr/bin and /usr/lib itself. It knows that
> those go to /bin and /lib. If you change them, you're on your own.
Something happened after I switched the mounts to symlinks. It seemed like
setup was trying to create /usr/bin but couldn't because I already had a
symlink there. Or something.
-- John Wiersba
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -