Re: [gentoo-portage-dev] virtuals and dependencies dispaly

[Jason Stubbs]

On Monday 23 October 2006 16:26, Brian wrote:
> I've been improving portholes dependency display, adding more info to
> it.  I've run into a minor snag when virtuals are concerned.  There also
> seems to be 2 sources of virtuals.  Both are not identical to each
> other:
>
> /usr/portage/virtual -- which seem to be packages.

They are just regular packages.

> virtuals = portage.db[portage.root]["virtuals"]  from
> gentoolkit.__init__.py

I'm not sure exactly what this returns, but it's probably equivalent to 
portage.settings.virtuals.

> I've found virtuals in the tree that are not in portages virtuals and
> vice-versa.
> Is there an order to their use by portage?

atom = "virtual/portage"
non_virtual_atom = portage.dep_virtual([atom], portage.settings)[0]

if atom == non_virtual_atom:
	print atom,"is a 'new style' virtual (aka regular package)"
else:
	print atom,"is an 'old style' virtual that resolves to',
	print non_virtual_atom

> Can the ones in the tree be
> treated as a category/package for listings, etc..  The ones in the tree
> do seem to be returned by:
>
> portage.db['/']['porttree'].getallnodes()[:] # copy
>
> The main reason I am looking at this is for indicating the dependency
> installed/needed for the virtual.  If an installed one is found I use
> it's package name. If not  where should I get it?  From the virtuals in
> portage or the tree? both? - then which order?

The ones in the tree are just regular packages - but may also exist in the 
PROVIDE attribute of associated ebuilds. As for ordering, packages with 
PROVIDE override identically named packages in the tree. If you use something 
similar to the above, it should all be taken care of though.

--
Jason Stubbs
-- 
gentoo-portage-dev@g.o mailing list