Re: Auto install code
Jason Gunthorpe wrote:
>
> So far things are going extremely well btw, with the code right now it is
> possible to upgrade to hamm in about 20 key strokes! Dselect for the same
> process is a bit of a nightmare I belive :>
Cool!
> A simple example, lets say you have two packages, libc6 and MyPackage that
> has an older version installed that depends on libc5 and has a new version
> that depends on libc6:
>
> 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 guess I imagined that libc6 would be installed automatically the first
time that someone upgraded a package that dependended on libc6.
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.
Behan
--
Behan Webster mailto:behanw@verisim.com
+1-613-224-7547 http://www.verisim.com/
Reply to: