public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* baffling cygwin setup.exe behavior
@ 2013-10-08 18:46 Don Hatch
  2013-10-08 19:13 ` Larry Hall (Cygwin)
  2013-10-08 19:43 ` Ryan Johnson
  0 siblings, 2 replies; 3+ messages in thread
From: Don Hatch @ 2013-10-08 18:46 UTC (permalink / raw)
  To: cygwin; +Cc: Don Hatch

I've always been baffled by cygwin setup's behavior.
I wish I understood it and could control it.

Here is a typical example where I want to do something
very simple and I have no idea how to get the setup program
to do it.  Help!

My goal: upgrade rcs to the "currently considered most stable"
version, without changing anything else on the system.

Here is what I tried, in excruciating detail.

I run "cygcheck -c rcs", which outputs:
    Cygwin Package Information
    Package              Version        Status
    rcs                  5.7-11         OK
I run cygwin setup-x86.exe.
The splash window says "Setup.exe version 2.829 (32 bit)".
   I click Next.
On the next window I select "Install from Internet",
   and click Next.
On the next window I select
   Root Directory: C:\cygwin
   Install For: All Users
   and click Next.
On the next window I select
   Local Package Directory: C:\Users\hatch\Downloads
   and click Next.
On the next window I select "Direct Connection"
   and click Next.
On the next window I select the download site
   http://cygwin.mirrors.hoobly.com
   and click Next.
It quickly downloads some stuff and
   puts me in the "Select Packages" window,
   with the "Curr" radio button selected and View=Category.

First I browse around to see what the "Curr" world looks
like (i.e. "Globally select the version that is currently
considered the most stable. (RECOMMENDED)" according
to the tooltip):
I open the Devel folder and scroll down to the "rcs" row,
which says:
   Current = 5.7-11
   New = <arrows> 5.8.2-1
   Bin? = [X]
   Src? = [ ]
   Size = 286k
   Package = rcs: The Revision Control system
So far I think this makes sense:
yes, I have 5.7-11 installed, and I want to upgrade to 5.8.2-1.
I click on the "<arrows> 5.8.2-1" to see what other
possibilities are available for this package.
It goes through the following values:
   <arrows> 5.8.2-1   (initial value)
   <arrows> Keep
   <arrows> 5.8.1-1
   <arrows> Uninstall
   <arrows> Keep
   <arrows> 5.8.1-1
   <arrows> Uninstall
   ...
Huh?  Once I've clicked it once,
it never cycles back to the initial value
of 5.8.2-1.  So that's baffling thing #1.
(The only way I can see to get it to show 5.8.2-1 again
is to globally change from "Curr" to something else
and then back to "Curr".)

Next, I change the global radio button
from "Curr" to "Keep"
(i.e. "Sets all packages to their currently installed version.
This is equivalent to telling setup not to make any changes
to any package." according to the tooltip).
I think this is the right thing to do
since since I don't want to change any packages except rcs--
I figure I will now be able to change just rcs individually.

I open the Devel folder again and scroll down to the "rcs" row,
which now says:
   Current = 5.7-11
   New = <arrows> Keep
   Bin? = n/a
   Src? = n/a
   Size = ?
   Package = rcs: The Revision Control System
When I click on the "<arrows> Keep" it cycles through:
   <arrows> Keep      (initial value)
   <arrows> 5.8.1-1
   <arrows> Uninstall
   <arrows> Keep
   <arrows> 5.8.1-1
   <arrows> Uninstall
   ...
Huh?  My desired value of 5.8.2-1 isn't available
from here at all???  That's baffling thing #2.

So, as far as I can see,
the only way to get rcs 5.8.2-1 is to globally select "Curr"
and *don't click on rcs at all*.
So, to upgrade rcs and nothing else,
I'd have to globally select "Curr"
and manually change every package *except* rcs
to "Keep", leaving rcs alone.
That seemed like a lot of work and error prone,
and I knew I was going to be doing all this several times,
and who knows whether I'd run into other problems on the way.
So instead, I elected to upgrade
my entire system to "Curr", even though
that's not really what I wanted.

If anyone can explain what's going on here
(is this a bug? or something wrong with my thinking?)
and how to do this simple operation,
I'd really appreciate it.

Don

-- 
Don Hatch
hatch@plunk.org
http://www.plunk.org/~hatch/

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: baffling cygwin setup.exe behavior
  2013-10-08 18:46 baffling cygwin setup.exe behavior Don Hatch
@ 2013-10-08 19:13 ` Larry Hall (Cygwin)
  2013-10-08 19:43 ` Ryan Johnson
  1 sibling, 0 replies; 3+ messages in thread
From: Larry Hall (Cygwin) @ 2013-10-08 19:13 UTC (permalink / raw)
  To: cygwin

On 10/8/2013 2:52 PM, Don Hatch wrote:

<snip>

> So, as far as I can see,
> the only way to get rcs 5.8.2-1 is to globally select "Curr"
> and *don't click on rcs at all*.
> So, to upgrade rcs and nothing else,
> I'd have to globally select "Curr"
> and manually change every package *except* rcs
> to "Keep", leaving rcs alone.
> That seemed like a lot of work and error prone,
> and I knew I was going to be doing all this several times,
> and who knows whether I'd run into other problems on the way.
> So instead, I elected to upgrade
> my entire system to "Curr", even though
> that's not really what I wanted.
>
> If anyone can explain what's going on here
> (is this a bug? or something wrong with my thinking?)
> and how to do this simple operation,
> I'd really appreciate it.

I'm not sure why you cannot get back to 5.8.2-1.  I can but I
don't have 'rcs' installed so my cycle just goes from Skip->
5.8.2-1->5.8.1-1->Skip->....

I guess if all else fails, try uninstalling and reinstalling
'rcs'.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: baffling cygwin setup.exe behavior
  2013-10-08 18:46 baffling cygwin setup.exe behavior Don Hatch
  2013-10-08 19:13 ` Larry Hall (Cygwin)
@ 2013-10-08 19:43 ` Ryan Johnson
  1 sibling, 0 replies; 3+ messages in thread
From: Ryan Johnson @ 2013-10-08 19:43 UTC (permalink / raw)
  To: cygwin

On 08/10/2013 2:52 PM, Don Hatch wrote:
> I've always been baffled by cygwin setup's behavior.
> I wish I understood it and could control it.
>
> Here is a typical example where I want to do something
> very simple and I have no idea how to get the setup program
> to do it.  Help!
>
> My goal: upgrade rcs to the "currently considered most stable"
> version, without changing anything else on the system.
>
> Here is what I tried, in excruciating detail.
Something tells me this isn't easily done.

... just be glad that neither RCS nor any of the unwanted upgrades had 
dependencies. They don't get unflagged when you go to "keep" and there's 
no option to only download the deps for some packages...

Ryan


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-10-08 19:43 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-10-08 18:46 baffling cygwin setup.exe behavior Don Hatch
2013-10-08 19:13 ` Larry Hall (Cygwin)
2013-10-08 19:43 ` Ryan Johnson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).