Re: Using smart within an SDK

[randy.e.witt@linux.intel.com]

> On Thu, May 14, 2015 at 7:54 PM, ChenQi <Qi.Chen@windriver.com> wrote:
>> The rpm database is not usable. You do a query to list files that a
>> package
>> installed and you will find all the paths are not correct.
> Ah okay---that makes sense.  Thanks.
>>
>> We are now working a new kind of SDK in OE. We call it extensible SDK.
>> By
>> design, its components could be updated/installed/removed using sstate
>> objects. The task is not completed yet, but we are working on it.
>
> I'd seen the extensible SDK and was thinking it looked pretty cool so
> I'll give this a whirl.  From what I've read, it doesn't yet support
> updating.  Is there a roadmap for this (happy to help out if I'm
> able)?  I'd also need to maintain an online sstate cache to make this
> SDK useful to others correct?
> --

The idea is that an sdk will comprise of a manifest(contains list of
sstate items in the sdk) and some location that contains the items in the
manifest. So to update the sdk you would run a command and give it the
location of the manifest and sstate, and it would make your sdk match what
is in the manifest.

So the sstate could be hosted on a webserver, nfs, locally, etc.

> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>