Re: Depends expansion and Virtual Packages
Jason Gunthorpe wrote:
>
> However, how should virtual packages be handled? They can't be selected
> for installation so what should be done? One option that comes to mind is
> to have a 3rd level of expansion where you can expand the virtual package
> list to see all of the possible canidates..
Yes, that is precisely what should be done.
> <snapshot from text version>
> Package Cur-Version Inst-Version
> Unknown x
> -*-|egcc 1.0-1 x
> -*-||gcc 2.7.2.3-3 x
> -|||libc5-dev x
> -|||libg++27-dev 2.7.2.1-8 x
> -|||libg++-dev x
> -|||libc-dev x
> -*-|||libc6 2.0.5c-0.1 x
> -*-|||cpp 2.7.2.3-3 x
> -*-|||cpp 2.7.2.3-3 x
> -*-|||binutils 2.8.1.0.15-1 x
> -||libc5-dev x
> -||libstdc++-dev x
> -||libc-dev x
> -*-||libc6 2.0.5c-0.1 x
> -*-||binutils 2.8.1.0.15-1 x
> -*-|kernel-image-2.0. 1.00 x
> -*-|libstdc++2.8 1.0-1 x
> -*-|libstdc++2.8-dev 1.0-1 x
> -*-|pgp-i 2.6.3a-1 x
> -*-|rxvt-cursorpad 2.20-4.2 x
> -*-|xv 3.10a-15 x
> libg++-dev and libc-dev are virtual packages. cpp is shown twice because
> gcc has a line like:
> Depends: libc6, cpp (>= 2.7.2.3-1), cpp (<< 2.7.2.4), binutils (>=2.8-1)
Expand virtual packages as you suggested above.
It would be good to make sure packages don't show up twice. (Although
I'm sure that is something you were going to do anyways. 8)
> Arg, this is going to be painfull! :> The tree display will not show the
> version target information from the dep (?)
I don't think I understand what you mean?
> Apparently libc5-dev is obsolete and no longer exists in anyform (how
> should that look?) Oh hmfr, there are 13 packages that depend on it too..
An obsolete package should have a delete checkbox (the user can only
remove the package or leave it how it is), and the inst-version should
have "obsolete" printed in it (along with the obsolete icon).
Later,
Behan
--
Behan Webster mailto:behanw@verisim.com
+1-613-224-7547 http://www.verisim.com/
Reply to: