delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2000/07/26/09:53:14

Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Wed, 26 Jul 2000 09:39:43 -0400
Message-Id: <200007261339.JAA17361@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cygwin-developers AT sources DOT redhat DOT com
In-reply-to: <20000725223226.D3868@cygnus.com> (message from Chris Faylor on
Tue, 25 Jul 2000 22:32:26 -0400)
Subject: Re: sample setup "version chooser"
References: <200007250153 DOT VAA10202 AT envy DOT delorie DOT com> <20000725223226 DOT D3868 AT cygnus DOT com>

> I didn't really "get it" until I read your description.

Right.  That's why I supplied one.

> I don't know if that is a problem or not.  Will there be more words
> and descriptions around the entries?  Or, maybe all that is needed
> is a "Help" button.

The final dialog will have helpful text on it.  A help button is a
possibility.

> >If the user selects to install a package that isn't installed by
> >default, should it get upgraded automatically by default after that?
> >Same for uninstalling a package that's installed by default.
> 
> Bleah.  Sounds like another button?  Or maybe an additional dialog
> box after the user moves off of this dialog:

No, I was thinking of having setup infer this information and store it
somewhere.  Thus, the fact that you elected to install or not install
something means that that should be the default from now on.

> >You can't have different default trust levels for each package.
> >I.e. you can't automatically get new experimental releases for some
> >packages, but stick with stable releases for others.
> 
> Hmm.  I think this would be pretty important.  If Chuck Wilson wanted
> people to try out a new version of libpng, it might be nice to just
> run setup to get that, while keeping everything else the same.

Yes, it will default to keep whatever you already have installed,
installed.  Exception: what you have installed has been superceded by
a new release.  So, if you are already up to date, and you choose to
upgrade to an experimental "vim" for example, setup will remember that
you've installed that version of vim, and as long as it remains
availble in setup.ini - either experimental or stable - setup will let
you keep it.  If, for some reason, it's removed from the ftp servers
and setup.ini, setup with then - and only then - re-install the stable
version.

However, it does this by remembering the version of the package you
installed, not the trust level.  It doesn't know that "vim-20000725"
was experimental, just that (1) you chose to install it, (2) it is
still a valid option, and (3) nothing has replaced it yet.

What setup won't do is automatically install a *new* experimental
version, just because you choose to install an experimental version
before.  Unless, of course, you default to choosing experimental
versions for *everything*.

> >You can't easily choose a new trust level while looking at the list of
> >packages.  If this is a popular request, I may rewrite the code to
> >support it, but at the moment it's all picked at startup.
> 
> I think this would be a nice feature too.  I'll bet that people would
> expect this.

Yeah, I figured.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019