Re: Autoinstall, upgrade, etc
On Thu, 4 Dec 1997, Behan Webster wrote:
> Jason Gunthorpe wrote:
> >
> > > 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?
> >
> > Both :> I like the greying of the inst button. This might be fun because
> > some packages still depend on the obsolete 'elf-x11r6' library. Deity will
> > immediately mark these for removal and prevent you from installing them
> > <hmmm, uh oh>
>
> Don't forget that obsolete packages are not auto-deinstalled. They are
> only marked as being obsolete. It is up to the user to uninstall them.
>
> Why would anything be marked for removal? The only time things are
> auto-removed is if nothing else depends on them any more (and if they
> were originally auto-installed).
>
> The only time I would suggest making it so you couldn't install a
> package is if all the "Depends on" (as per the header) packages are not
> available or being kept back to previous versions. And then I would
> also include an override.
>
> I don't understand when your example would occur.
Well, this is silly but:
elf-x11r6 used to be provided by xlib.
xlib no longer provides it
packages still depend on it
dpkg allowed you to upgrade to the new xlib even though it would wreck
dependancies
in fact dpkg didn't even warn you that you were doing something silly.
So to the view of any sane person a package that depends on elf-x11r6 and
is installed in the system is broken. Deity should remove packages in a
state like this they are held with a keep-force.
Basically, if you dpkg --force-?? <package> and then load deity it should
attempt to remove the packages that have been broken by the dpkg --force.
The user will have to keep-force (new idea?) the package to stop this.
Oh, if deity detects a new version (in any dist?) then I suppose it could
somehow mark it for install, donno..
Is that okay?
The automatic 'fixing' of systems is going to be very hard to get just
right so lots'o'fiddling.
BTW, did you ever get the sources to compile or try to run Scott's .debs?
Jason
Reply to: