Re: Auto install code
On Fri, 16 Jan 1998, Behan Webster wrote:
> Jason Gunthorpe wrote:
> > DKI Package
> > -*- - MyPackage
> > - `- libc6
> > - libc6
> >
> > (that is how it would actually look). Lets say you hit intall on libc6,
> >
> > DKI Package
> > --* - MyPackage
> > * `- libc6
> > * libc6
> >
> > As you can see by installing libc6 you allowed MyPackage to upgrade so
> > deity changed it to upgrade. Now lets say you undo that immedately,
> >
> > DKI Package
> > --* - MyPackage
> > - `- libc6
> > - libc6
> >
> > Uh oh! It didn't undo the upgrade to MyPackage it did seconds earlier.
> > MyPackage will now be listed as 'broken' and be shown in red and Deity
> > will complain when you attempt to do the installations.
> >
> > This doesn't seem to be very nice..
>
> I think this is a bit of a red herring. Hopefully people won't be
> manually upgrading dependent packages. In this case, it would be more
> of a matter of libc6 being auto-installed if MyPackage is installed.
> Personally, I would have it such that the user never sees the libc6
> package in the selection list except as a dependency of something else.
I can arrange for auto packages to be hidden unless a list menu option is
selected if you like?
> I guess I imagined that libc6 would be installed automatically the first
> time that someone upgraded a package that dependended on libc6.
It is. But the user has to explicly ask that a package depending on libc6
be upgraded. The autoupgrader will not install new packages to try to make
other packages upgradable. If you want this then please tell me :>
We could redo the example and have the user upgrade MyPackage (instead of
installing libc6) which would cause libc6 to be installed and then have
the user undo their action and notice that libc6 was not automatically
removed.
You might think the auto mechanism would deal with this, but what happens
is that once libc6 is installed many other packages suddenly get upgraded
so libc6 is 'used'.
> I think what I'm understanding is that MyPackage wasn't auto-upgraded
> because it was felt that libc6 would break something. Am I right? If
> so, then my feeling is that it's up to the user to catch this problem.
MyPackage was not upgraded because doing so would require libc6 to be
installed automatically.
Do you want deity to attempt -REALLY- hard to upgrade packages? Right now
it is very wimpy and will not install, remove, etc anything to make an
upgrade go through.
It is however very agressive when the user asks it to do something and
will remove, install and upgrade any package.
Jason
Reply to: