Re: The Deity tree widget
On Tue, 18 Nov 1997, Behan Webster wrote:
> Jason Gunthorpe wrote:
> I'm afraid I don't understand the question. Sorry.
Okay, I'll ask you later when I have something to show..
> Yes. If we use the +/- then the dep/whatever icons will go to the right
> of the +/- just like in the linux Explorer. As you say, what is
> currently in my web pages is a bit confusing. It was more of an
> experiment. A failed experiment IMHO.
Are triangles any different, placement wise, then +/- ? (I'm just goint to
use +/- as a generic term for the icons whatever they end up being.)
> Identifying new packages shouldn't be a problem. Should it? If you have
> to add a file to your cache (because it wasn't there on the previous
> running of deity) surely you can assume it's a new package. Or am I
> missing something?
Well, to handle removing of versions and other changes the whole cache is
erased and rebuilt. The new generator is going to have to keep a copy of
the old one and then rebuilt the new one, cross reference to find new
packages.
Do new versions get a new mark or only new packages?
> > Hm, but how can the user do this if there is no version to upgrade? I
> > think you said that in the case of an installed package, with no
> > upgradeable version there would be a checkbox on remove, which means there
> > is no option to 'keep'.
> True. However, if there is no version to upgrade to, why is there a
> problem?
Okay, you tell me then, here are 3 different (cronological) invokations
of deity:
RIK
-*- libc 1.0 ^ 1.1
--* libc 1.0 ^ 1.1
- libc 1.0
-?? libc 1.0 ^ 1.1
The first item is the initial state, the user selects keep to prevent
upgrading in the second item. The next item the user has changed something
so that the package is no longer upgradable. The fourth item the user has
undone their change.
Please tell me what the 4th item should show. I would think --* would be
intuitive.
Also, Are the above states okay?
--- <-- 3 radio buttons, * = current
- <-- Single checkbox, * = checked
And while we are at it, here is the last possible state:
- libc ^ 1.0
Now, a feature seems to be missing, given that deity is supposed to
automatically select packages for upgrade and install based on other
selections how can this be prevented on a per-package scale? (Think:
Package is not installed, user wants to ensure that package is -never-
installed, ie Bruce might not want to go through his ritualistic cleansing
again so he would make QT as being uninstallable to ensure it never gets
installed automatically :| )
Jason
Reply to: