On Sat, 21 Jan 2006, Brian Dessent wrote:
> Urs Rau wrote:
>
> > Is there any mechanism at all where I can either tell setup.exe to
> > ignore future versions of posgresql or else actually be as precise, as
> > to tell it that I want to stay at version 7.x for now?
>
> No, sorry. It will try to install "curr" by default every time,
> whatever version that happens to be.
IIRC, if there are two "curr" versions, setup picks the one from the first
setup.ini it encounters. I wonder, if there's a way to create a custom
setup.ini file with the fixed version as "curr", and then ensure that it's
found first, would setup keep it locked?
In any case, I think I can whip up some quick and dirty code to do the
locking in a day or so, but I think that may do more harm than good...
To do this properly, setup should at least give warnings when a dependency
of a locked version is updated. I'll send the patch in the next couple of
days, but we shouldn't release a new version until the dependency checking
is in place.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
