This is the mail archive of the
mailing list for the Cygwin project.
RE: Blind people using setup.exe?
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Dave Korn <dave dot korn at artimi dot com>
- Cc: cygwin-apps at cygwin dot com
- Date: Mon, 27 Jun 2005 13:06:48 -0400 (EDT)
- Subject: RE: Blind people using setup.exe?
- References: <SERRANO6PBJBd3VO4W20000021d@SERRANO.CAM.ARTIMI.COM>
- Reply-to: cygwin-apps at cygwin dot com
On Mon, 27 Jun 2005, Dave Korn wrote:
> ----Original Message----
> >From: Igor Pechtchanski
> >Sent: 27 June 2005 17:27
> > On Mon, 27 Jun 2005, Nikhil Nair wrote:
> >> On Sun, 26 Jun 2005, Igor Pechtchanski wrote:
> >>> Assuming you have the ability to edit files, as a temporary workaround
> >>> you could add the following line to your /etc/setup/installed.db (in
> >>> alphabetical order):
> >>> emacs emacs-0-0.tar.bz2 0
> >>> and re-run setup. It should now "upgrade" the version of emacs it
> >>> thinks you have (0-0), effectively installing emacs.
> >>> HTH,
> >>> Igor
> >> Thanks, Igor - that workaround performed flawlessly.
> >> Am I right in suspecting that, if I were to use this method for another
> >> package which had unsatisfied dependencies, setup.exe wouldnt' sort out
> >> those dependencies for me? Or would it assume the dependencies had
> >> changed since version 0-0, and handle them seamlessly?
> > I'm hoping it's the latter, but don't have the opportunity to verify that
> > right now. You can easily test that hypothesis yourself (just look in any
> > setup.ini file in your local package cache for the dependency
> > information)... :-)
> You know, this sounds like such a useful feature/hack/workaround that
> I'm tempted to write a patch for setup that allows it to be done by a
> command-line option.
Glad you think so. FWIW, if it becomes a command-line option, there won't
be any need to edit installed.db -- just add the package to the list of
those needing to be upgdaded (see the installed.db parsing code).
> Oh, that reminds me, --no-md5 is broken, I just noticed the other day
> - gotta look at that too.
Hehe. While we're at it, would you like to make setup print out a list of
its command-line options, either in a message box or by doing an
AllocConsole()? I know the latter approach will pop up a console box if
setup is started from a pty or via a shortcut (which will go away once the
output is done), but it's better than nothing, and should work just fine
if setup is started from a console shell.
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT