So, I'm not 100% sure yet, but it appears to me that if you have a large list of "attempt-only" packages, and *any* of them can't be found at all, opkg bails out without doing anything about the rest of them.
This seems a little surprising, because my assumption would be that the expected behavior for "attempt-only" packages would be to try to install as many as possible. Looking at other cases, it looks like the RpmPM and related code try to handle each package separately to build a list, but OpkgPM doesn't. I note also that RpmPM will allow an empty list of mandatory packages, while OpkgPM only accepts an empty list when attempt_only is True. This affects us because we have a setup in which we put a very large pool of packages in as attempt-only because we know that there will be small variances in package lists which are hard to anticipate, and the net result is that none get installed at all. -s -- Listen, get this. Nobody with a good compiler needs to be justified. -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
