First, the code to walk the groups is enough to use.
On Sun, Mar 02, 2014 at 03:46:54PM +0100, Mark Trompell wrote:
> Am Sat, 1 Mar 2014 17:56:01 -0500
> schrieb "Michael K. Johnson" <[email protected]>:
> > In the group, we'll be doing something like:
Emphasis on the "something like" as what I wrote wasn't tested,
and was actually only intended to show what the context might
be like.
> groups = []
...
> r.Group(groups)
I led you astray. The groups need to be either summed or unioned...
I haven't tested this syntax either, but I think it will work.
r.Group(sum(groups))
That said, since we haven't actually imported all the packages
yet, it is bound to fail.
As we discussed on IRC, for all the repodata-based groups, we plan
not to make them dependency-complete.
mirrorball will be writing a complete list of all packages that are
included in a slice of history (we won't be able to use "latest"
because sometimes updates are released out of order), and we'll
use that for the group of all packages. That will be the search
group.
We can, if we like, test for dependency closure by adding a line
something like allpackages.depsNeeded(allpackages) and throwing
away the results. It is not clear to me that we'll want to do
that.
_______________________________________________
Foresight-devel mailing list
[email protected]
https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
