Re: Autoinstall, upgrade, etc
Jason Gunthorpe wrote:
>
> On Tue, 2 Dec 1997, Behan Webster wrote:
>
> > Jason Gunthorpe wrote:
> > > > For example, I have sudo put on hold (since the new versions
> > > > of sudo fail to parse the config file); I would hate to have the
> > >
> > > We don't have a hold state only a keep state. Once a package is flagged
> > > 'keep' then that's it, there is no changing that [by deity, of course you
> > > can]. But you may only flag a package 'keep' if the package is installed
> > > and upgradeable. (see emails a week back on this)
> >
> > I was actualy thinking that a dependancy would force it from 'keep' to
> > 'inst' but the user would be warned of this by a message in the status
> > window, and on the installation screen.
>
> Hm, are you certain you want this?
I thought I was. Why? What are you're concerns? Perhaps we should
discuss this a bit. It seems this might be an important issue.
Everyone: Should "keep" be changed to "inst" automatically if an
upgraded package depends on the upgraded version of the "kept" package?
> > > Behan: How do you want selecting an uninstallable package for installation
> > > handled and other issues with impossible installation situations that
> > > cannot be resolved automatically?
> >
> > Give me an example of an "uninstallable package"?
>
> It's possible in two cases, both because a dependancy cannot be resolved
> 1) The target of a dependancy doesn't exist
i.e. a package (or a particular version of a package) is not available
even though an auto-install requires it?
This eventuality had not occurred to me. Hmmm.
At the very least, an error message about this should be listed in the
status window, and in the install screen. Something like "unresolvable
dependancy".
I don't want dialog boxes popping up all over the place on errors, I
find that very irritating and it is generally considered bad UI style.
The options that come to mind are:
1) If a package cannot be upgraded due to a missing dependancy, then
gray out the "inst" button when you first draw the selection screen.
2) If on clicking the "inst" button deity determines that there is a
missing dependency, beep, and show an error message in the status bar.
Which of these options would be easier to implement?
In either case, we would have to provide a way for the user to override
this (perhaps another control in the status window).
> 2) The target is in the keep state
>
> #2 cannot happen if you want to force keep to inst.
Quite. If we decide otherwise, however, the answer to your 1st point
should cover this situation too.
> > I won't be able to respond to any email until tomorrow night-ish. I
> > have to stay home from work tomorrow to wait for the ADSL guys to come
> > and install my new toy! 8) I'm so excited!
>
> ooooooooooooooooooooooohhhhhhhhhhhhhhhhhhhhhhhhhhhhh ADSL!
Once I got it all working, it was awesome! I now have a home machine on
the net 24 hours a day! 8)
Damn finicky though. They had to rewire half my apartment to get the
damn thing to work! It took the poor ADSL install guy 4 hours to figure
out the peculiar phone wiring in my apartment. It is a very oddly wired
place. 8) But I don't care, I have ADSL at home now!!!
I'm not at all excited by it though. Ho hum...
> Now you can download Deity snapshots at obscene speeds!
Yep! 8)
Behan
--
Behan Webster mailto:behanw@verisim.com
+1-613-224-7547 http://www.verisim.com/
Reply to: