Re: non empty package group

Paul Eggleton

On Wednesday 16 April 2014 17:28:45 Katu Txakur wrote:
2014-04-16 17:17 GMT+01:00 Paul Eggleton <paul.eggleton@...>:
On Wednesday 16 April 2014 17:09:19 Katu Txakur wrote:
yes, it does "inherit packagegroup" and all the packages are installed.
What I would like to have is a mypackagegroup.ipk that I can copy to any
system to install all the files, binaries.... in those recipes using
"opkg install mypackage.ipk"
The problem that I have is that the files, binaries... of the recipes in
RDEPENDS_${PN} are not included in the mypackagegroup.ipk. Do you know
how can I include them?
opkg and similar package managers simply aren't designed to work like
that; it's expected that both devices would have access to the same
package feeds and therefore you would just install the packagegroup
package on each system in the same way.
I see, but I don't want to feed the package from a repo, I just want to
include all the files in the package.
I'm now trying to set
PREFERRED_PROVIDER_each-recipe = "mypackagegroup"
hoping that it will change the location of the files from their individual
recipes/packages to the packagegroup.
I've just cleaned the entire tmp folder, I will find out tomorrow if this
It isn't as simple as that, that just selects between providers but there is
nothing to actually make the "mypackagegroup" recipe actually provide
anything. The files would need to actually be produced as part of the
packagegroup recipe, and then it isn't really a packagegroup anymore.

I'm afraid our system just isn't designed to work this way. I'm sure it could
be made to, but it would require some additional work.



Paul Eggleton
Intel Open Source Technology Centre

Join { to automatically receive all group messages.