setup.exe selects old versions for required packages

setup.exe selects old versions for required packages

[Polley Christopher W]

I've just reinstalled cygwin today and was frustrated to find while
selecting packages to install from my local directory, when I changed a
package from skip to <version>, setup.exe selected the less-recent version
of all required packages (i.e., selecting automake requires autoconf, and
version 2.13-2 was brought up rather than the most recent 2.52-1)  

I ended up tediously going through the list of packages to select the ones I
wanted, then going through the entire list a second time cycling through
each and every selected package to make sure I had the latest version
selected.

Could selecting the most recent version of required packages as the default
behavior (when required packages are not already installed) please be added
to the setup.exe wish list?  

Has a version requirement (similar to RPM) been considered to alleviate the
installation problems seen with vim/gettext?

Warm Regards,
Chris



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: setup.exe selects old versions for required packages

[Robert Collins]

Most of this email has laready been addressed.

On Wed, 2001-11-28 at 02:28, Polley Christopher W wrote:
> Has a version requirement (similar to RPM) been considered to alleviate the
> installation problems seen with vim/gettext?

Yes, but we took the one-step at a time approach. Please note that a
version requirement will NOT solve the vim/gettext confusion. That
confusion was caused because setup doesn't check for file conflicts, and
in not checking for them, cannot take appropriate action (in this case,
upgrading the old package first, which would fix the conflict and
prevent the .dll getting inappropriately deleted).

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: setup.exe selects old versions for required packages

[Charles Wilson]

Robert Collins wrote:


> Yes, but we took the one-step at a time approach. Please note that a
> version requirement will NOT solve the vim/gettext confusion. That
> confusion was caused because setup doesn't check for file conflicts, and
> in not checking for them, cannot take appropriate action (in this case,
> upgrading the old package first, which would fix the conflict and
> prevent the .dll getting inappropriately deleted).


Maybe I am having a thinko, but I don't remember any file conflict in 
the gettext package.  ncurses(old)-->ncurses(new)+libncurses* had an 
"inappropriate .dll deletion" problem if you don't do things in the 
right order -- but I don't remember anything like that with gettext.

Help?

--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: setup.exe selects old versions for required packages

[Robert Collins]

----- Original Message -----
From: "Charles Wilson" <cwilson@ece.gatech.edu>
> Maybe I am having a thinko, but I don't remember any file conflict in
> the gettext package.  ncurses(old)-->ncurses(new)+libncurses* had an
> "inappropriate .dll deletion" problem if you don't do things in the
> right order -- but I don't remember anything like that with gettext.
>
> Help?

ncurses (old) has cygncurses5.dll.
ncurses (new) does not.
libncurses has cygncurses5.dll.

So if you install *both* ncurses (old) and libncurses, you have a file
conflict.

Avoiding that conflict was the goal of your specific order during the
upgrade process.

The inappropriate .dll deletion was a symptom that occured when the
conflict occured.

Setup should be able to handle that, and delay installing the libncurses
package until the upgrade to the new ncurses had been done, and then
retry the libncurses package to see if the conflict went away.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: setup.exe selects old versions for required packages

[Robert Collins]

----- Original Message -----
From: "Charles Wilson" <cwilson@ece.gatech.edu>
To: "Robert Collins" <robert.collins@itdomain.com.au>
Cc: "Polley Christopher W" <PolleyChristopherW@JohnDeere.com>;
<cygwin@cygwin.com>
Sent: Wednesday, November 28, 2001 8:17 PM
Subject: Re: setup.exe selects old versions for required packages


> Robert Collins wrote:
>
>
> > Yes, but we took the one-step at a time approach. Please note that a
> > version requirement will NOT solve the vim/gettext confusion. That
> > confusion was caused because setup doesn't check for file conflicts,
and
> > in not checking for them, cannot take appropriate action (in this
case,
> > upgrading the old package first, which would fix the conflict and
> > prevent the .dll getting inappropriately deleted).
>
>
> Maybe I am having a thinko, but I don't remember any file conflict in
> the gettext package.  ncurses(old)-->ncurses(new)+libncurses* had an
> "inappropriate .dll deletion" problem if you don't do things in the
> right order -- but I don't remember anything like that with gettext.
>
> Help?

Sorry, I need glasses I think. Yes Chuck, you're right, gettext was
completely different, I was confused and adding confusion :}. A minimum
version requirement for gettext in the vim requirements would solve the
cygintl.dll problem, done either the rpm or deb fashion.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

setup.exe selects old versions for required packages

[Polley Christopher W]

I've just reinstalled cygwin today and was frustrated to find while
selecting packages to install from my local directory, when I changed a
package from skip to <version>, setup.exe selected the less-recent version
of all required packages (i.e., selecting automake requires autoconf, and
version 2.13-2 was brought up rather than the most recent 2.52-1)  

I ended up tediously going through the list of packages to select the ones I
wanted, then going through the entire list a second time cycling through
each and every selected package to make sure I had the latest version
selected.

Could selecting the most recent version of required packages as the default
behavior (when required packages are not already installed) please be added
to the setup.exe wish list?  

Has a version requirement (similar to RPM) been considered to alleviate the
installation problems seen with vim/gettext?

Warm Regards,
Chris



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: setup.exe selects old versions for required packages

[Robert Collins]

Most of this email has laready been addressed.

On Wed, 2001-11-28 at 02:28, Polley Christopher W wrote:
> Has a version requirement (similar to RPM) been considered to alleviate the
> installation problems seen with vim/gettext?

Yes, but we took the one-step at a time approach. Please note that a
version requirement will NOT solve the vim/gettext confusion. That
confusion was caused because setup doesn't check for file conflicts, and
in not checking for them, cannot take appropriate action (in this case,
upgrading the old package first, which would fix the conflict and
prevent the .dll getting inappropriately deleted).

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: setup.exe selects old versions for required packages

[Charles Wilson]

Robert Collins wrote:


> Yes, but we took the one-step at a time approach. Please note that a
> version requirement will NOT solve the vim/gettext confusion. That
> confusion was caused because setup doesn't check for file conflicts, and
> in not checking for them, cannot take appropriate action (in this case,
> upgrading the old package first, which would fix the conflict and
> prevent the .dll getting inappropriately deleted).


Maybe I am having a thinko, but I don't remember any file conflict in 
the gettext package.  ncurses(old)-->ncurses(new)+libncurses* had an 
"inappropriate .dll deletion" problem if you don't do things in the 
right order -- but I don't remember anything like that with gettext.

Help?

--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: setup.exe selects old versions for required packages

[Robert Collins]

----- Original Message -----
From: "Charles Wilson" <cwilson@ece.gatech.edu>
> Maybe I am having a thinko, but I don't remember any file conflict in
> the gettext package.  ncurses(old)-->ncurses(new)+libncurses* had an
> "inappropriate .dll deletion" problem if you don't do things in the
> right order -- but I don't remember anything like that with gettext.
>
> Help?

ncurses (old) has cygncurses5.dll.
ncurses (new) does not.
libncurses has cygncurses5.dll.

So if you install *both* ncurses (old) and libncurses, you have a file
conflict.

Avoiding that conflict was the goal of your specific order during the
upgrade process.

The inappropriate .dll deletion was a symptom that occured when the
conflict occured.

Setup should be able to handle that, and delay installing the libncurses
package until the upgrade to the new ncurses had been done, and then
retry the libncurses package to see if the conflict went away.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: setup.exe selects old versions for required packages

[Robert Collins]

----- Original Message -----
From: "Charles Wilson" <cwilson@ece.gatech.edu>
To: "Robert Collins" <robert.collins@itdomain.com.au>
Cc: "Polley Christopher W" <PolleyChristopherW@JohnDeere.com>;
<cygwin@cygwin.com>
Sent: Wednesday, November 28, 2001 8:17 PM
Subject: Re: setup.exe selects old versions for required packages


> Robert Collins wrote:
>
>
> > Yes, but we took the one-step at a time approach. Please note that a
> > version requirement will NOT solve the vim/gettext confusion. That
> > confusion was caused because setup doesn't check for file conflicts,
and
> > in not checking for them, cannot take appropriate action (in this
case,
> > upgrading the old package first, which would fix the conflict and
> > prevent the .dll getting inappropriately deleted).
>
>
> Maybe I am having a thinko, but I don't remember any file conflict in
> the gettext package.  ncurses(old)-->ncurses(new)+libncurses* had an
> "inappropriate .dll deletion" problem if you don't do things in the
> right order -- but I don't remember anything like that with gettext.
>
> Help?

Sorry, I need glasses I think. Yes Chuck, you're right, gettext was
completely different, I was confused and adding confusion :}. A minimum
version requirement for gettext in the vim requirements would solve the
cygintl.dll problem, done either the rpm or deb fashion.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/